Cant Bind to IP address

Get help with connectivity problems.
Posts: 1
Joined: Thu Oct 29, 2015 10:31 am

Cant Bind to IP address

Postby Evan Roggenkamp » Thu Oct 29, 2015 10:35 am

2015-10-29T12:31:45] ERROR: failed to get desktop path, no drop target available, error=2
[2015-10-29T12:31:45] FATAL: failed to start server: cannot bind address: The specified address is not available from the local machine

All of my network adapters besides the primary are disabled.
I have it configured as a server; the IP address that Synergy shows is correct. I am configuring interactively.
This is on Windows 7 Enterprise SP1.

C:\Windows\system32>netstat -n

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:1035 127.0.0.1:5354 ESTABLISHED
TCP 127.0.0.1:1038 127.0.0.1:5354 ESTABLISHED
TCP 127.0.0.1:1057 127.0.0.1:1058 ESTABLISHED
TCP 127.0.0.1:1058 127.0.0.1:1057 ESTABLISHED
TCP 127.0.0.1:1059 127.0.0.1:1060 ESTABLISHED
TCP 127.0.0.1:1060 127.0.0.1:1059 ESTABLISHED
TCP 127.0.0.1:1061 127.0.0.1:1062 ESTABLISHED
TCP 127.0.0.1:1062 127.0.0.1:1061 ESTABLISHED
TCP 127.0.0.1:1063 127.0.0.1:1068 ESTABLISHED
TCP 127.0.0.1:1068 127.0.0.1:1063 ESTABLISHED
TCP 127.0.0.1:1077 127.0.0.1:47007 ESTABLISHED
TCP 127.0.0.1:1169 127.0.0.1:4573 ESTABLISHED
TCP 127.0.0.1:1173 127.0.0.1:5939 ESTABLISHED
TCP 127.0.0.1:1175 127.0.0.1:1176 ESTABLISHED
TCP 127.0.0.1:1176 127.0.0.1:1175 ESTABLISHED
TCP 127.0.0.1:1177 127.0.0.1:1178 ESTABLISHED
TCP 127.0.0.1:1178 127.0.0.1:1177 ESTABLISHED
TCP 127.0.0.1:1420 127.0.0.1:24801 ESTABLISHED
TCP 127.0.0.1:1475 127.0.0.1:5354 ESTABLISHED
TCP 127.0.0.1:1476 127.0.0.1:5354 ESTABLISHED
TCP 127.0.0.1:4573 127.0.0.1:1169 ESTABLISHED
TCP 127.0.0.1:5354 127.0.0.1:1035 ESTABLISHED
TCP 127.0.0.1:5354 127.0.0.1:1038 ESTABLISHED
TCP 127.0.0.1:5354 127.0.0.1:1475 ESTABLISHED
TCP 127.0.0.1:5354 127.0.0.1:1476 ESTABLISHED
TCP 127.0.0.1:5939 127.0.0.1:1173 ESTABLISHED
TCP 127.0.0.1:24801 127.0.0.1:1420 ESTABLISHED
TCP 127.0.0.1:47007 127.0.0.1:1077 ESTABLISHED
TCP 172.26.61.130:1105 184.172.60.198:5938 ESTABLISHED
TCP 172.26.61.130:1130 192.168.148.175:445 ESTABLISHED
TCP 172.26.61.130:1152 192.168.148.171:445 ESTABLISHED
TCP 172.26.61.130:1154 192.168.148.172:445 ESTABLISHED
TCP 172.26.61.130:1156 192.168.148.174:445 ESTABLISHED
TCP 172.26.61.130:1165 192.168.148.152:49163 ESTABLISHED
TCP 172.26.61.130:1201 74.125.69.188:5228 ESTABLISHED
TCP 172.26.61.130:1233 216.58.216.78:443 ESTABLISHED
TCP 172.26.61.130:1309 199.59.149.230:443 ESTABLISHED
TCP 172.26.61.130:1369 199.59.150.44:443 ESTABLISHED
TCP 172.26.61.130:1431 216.58.216.68:443 ESTABLISHED
TCP 172.26.61.130:1432 64.233.191.141:443 ESTABLISHED
TCP 172.26.61.130:1435 216.58.216.65:443 ESTABLISHED
TCP 172.26.61.130:1440 216.58.216.78:443 ESTABLISHED
TCP 172.26.61.130:1441 216.58.216.68:443 ESTABLISHED
TCP 172.26.61.130:1442 216.58.216.67:443 ESTABLISHED
TCP 172.26.61.130:1445 216.58.216.78:80 ESTABLISHED
TCP 172.26.61.130:1447 216.58.216.78:443 ESTABLISHED
TCP 172.26.61.130:1448 216.58.216.78:443 ESTABLISHED
TCP 172.26.61.130:1452 54.221.225.63:443 ESTABLISHED
TCP 172.26.61.130:1453 54.221.225.63:443 ESTABLISHED
TCP 172.26.61.130:1455 64.233.191.95:80 ESTABLISHED
TCP 172.26.61.130:1459 216.58.216.67:80 ESTABLISHED
TCP 172.26.61.130:1467 216.58.216.78:443 ESTABLISHED
TCP 172.26.61.130:1492 204.93.75.156:443 ESTABLISHED
TCP 172.26.61.130:1493 216.58.216.202:443 TIME_WAIT
TCP [::1]:1279 [::1]:1281 ESTABLISHED
TCP [::1]:1281 [::1]:1279 ESTABLISHED

Posts: 2
Joined: Mon Nov 28, 2016 4:07 pm

Re: Cant Bind to IP address

Postby Rob Hawkins » Mon Nov 28, 2016 4:13 pm

I see this question being asked a lot, but not being answered. In my case I got this error sequence:
Code: Select all
[2016-11-28T16:45:45] INFO: starting server
[2016-11-28T16:45:45] INFO: config file: C:/Users/Rob/AppData/Local/Temp/qt_temp.gq6136
[2016-11-28T16:45:45] INFO: log level: NOTE
[2016-11-28T16:45:46] INFO: activeDesktop:Default
[2016-11-28T16:45:46] ERROR: could not get session id for process id 16212
[2016-11-28T16:45:46] FATAL: failed to start server: cannot bind address: The specified address is not available from the local machine
[2016-11-28T16:45:47] ERROR: failed to launch, error: process immediately stopped

I found that I had the wrong address configured in "Edit > Settings" under "Interface".

I'm running Version 1.8.5-stable-a18eba7 as a Server on Windows 10 Home.

Return to Connectivity

Who is online

Users browsing this forum: No registered users and 1 guest