Synergy client keeps searching bad or old IP addresses for my Server (which is a laptop, with DHCP gets new IP regularly). Also my laptop has a couple "bad" ipaddress which are visible to other PC's when nslookup is done.
So the Synergy client just keeps trying to use these bad or old IP addresses and getting failed to connect to server errors. Eventually after 10 minutes or 30 or something after I give up and dig out another keyboard, the client will eventually get around to the good IP and will connect.
I think the Server application causing these "bad IP's" might be at fault here too (VMware)... it puts the virtual network IP's into WinXP's network connections which I think allows other PC's like my client see 192.168.XXX.1 which are meaningless to other computers.
Anyway.... can I make Synergy change its retry strategy??? Rather than retrying server IP address #1 for 100 times, then IP address #2 100 times, then etc.... I'd rather that it try IP #1 once, then try IP #2 once, then IP #3 once, then do the equivalent of nslookup for the server to see if it is visible with a new IP, then cycle through the list again.