Looking for a solution for remote work? See how Remote Utilities can help! (X) Dismiss

Community

Remote Utilities Viewer for Mac andLinux has been released. Send us your feedback and report bugs in this discussion thread.

Unable to start TCP server. Check port:

Vladimir N., User (Posts: 1)

Oct 23, 2018 1:38:32 am EDT

Support level: Free or trial
So I'm starting to test your solution and immediately struck the following - can't properly start the host as it says can't bind port - the same issue is with all other ports (tried several random)
Although those ports are not occupied in the system as per netstat -na report.
No antivirus, internal firewall enabled, admin access, windows 10 pro x64 1803 (updated to latest)

23.10.2018---05:20:48:504 105 Unable to start TCP server. Check port: 5650 Could not bind socket. Address and port are already in use.
23.10.2018---05:20:48:516 34 Remote Utilities - Host 69014 is started. GMT+04 Windows 10.0 64bit
23.10.2018---05:20:49:072 96 Internet-ID: Connection established ID: 687-262-260-ххх; Port: 5655; Try count: 1
23.10.2018---05:24:12:626 96 Internet-ID: loopback connect error ID: 127.0.0.1
23.10.2018---05:29:12:568 105 Unable to start TCP server. Check port: 5656 Could not bind socket. Address and port are already in use.

Any suggestions? On the remote side i can see that host added to address book as live.

Conrad, Support (Posts: 2491)

Oct 24, 2018 5:40:37 am EDT

Hello Vladimir,

Thank you for your message.  Please, check if you have "Use Ipv6" enabled and let us know.

Alternatively, just delete this registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities Host


and restart the Host with default settings (i.e do not change the port). Then check if it works.

* Website time zone: America/New_York (UTC -4)

This website uses cookies to improve user experience. By using this website you agree to our Terms of Service and Privacy Policy.