New install, error on starting "Failed to start server: Failed to bind port"

[Milburne]

New download of v1.0 install to Windows 7 Pro-64bit.

The full text in the error dialog is:
Failed to start server: Failed to bind port "192.168.254.24:42000"

The installed Warpinator.exe.config file does include a setting for "Port" as "42000". Should this be changed to another value and if so how determine one that should work?

Thank you.

EDIT: After restarting the Windows session, Warpinator loads without the error and displays available devices, but immediately displays a "Warpinator has stopped working" dialog box with the following details text:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: Warpinator.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 9ab34efe
Problem Signature 04: mscorlib
Problem Signature 05: 4.8.4069.0
Problem Signature 06: 5dc611cd
Problem Signature 07: 1693
Problem Signature 08: 1d8
Problem Signature 09: System.IO.IOException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: a63a
Additional Information 2: a63a939facc0011561ccce81ddb87480
Additional Information 3: e04f
Additional Information 4: e04f31ae4bf1eee491cea53569e87695

[slowscript]

Port is usually not an issue and should not be changed, more likely Warpinator has selected a wrong network interface that cannot be bound (see left half of status bar). You can change it in Warpinator's settings. As for the crash, version 1.0.1 should now display more useful information about what actually happened.

[Milburne]

Thank you. I will download version 1.0.1 and see if I can figure out what I may need to change.

[Milburne]

Upgrading the install on the Win7 box did actually fix the crash issue itself.

Scanning did not see the 4 linux mint machines on the LAN but I was able to add 3 of them manually. The one that could not be connected manually is the only LM 20.1 box and the only other one with a wired connection like the windows host.

The three that worked are all LM 22. I will be upgrading the v20.1 machine shortly so hopefully that will resolve that lingering problem here.

Thanks again, I will mark your response as the answer.