Feature Suggestion: Secondary initiated reconnect

from Stardock Forums
OK, so I've talked a bit about my "laptop woes" in the past. I think these come down to DHCP reassigning me a new IP address too often as I cross wireless router zones (going from home to work to home or going from building 1 to building 2...) combined with DHCP -> Dynamic DNS registration of these IP addresses not really working like it should (it's very frequent for me to ping my machine name and have an entirely different machine with my old IP address respond).

I'd like to suggest a "secondary laptop" enhancement for Multiplicity. It works on the theory that the Primary machine's IP address is staying stable (and DNS registered).

Basically how it might work is that when Multiplicity running on a secondary detects an IP Address change, it would ping the Primary and attempt to reconnect proactively. If after connection from the secondary the Primary determines that the secondary's ip address has changed (and it is set to manual configuration), the Primary would update the IP address setting.

Thoughts?
multiplicity
3,629 views 2 replies
Reply #1 from WinCustomize Forums Top
I added my secondary by machine name and set MP to look up the IP every time. That solved my issues of changing IPs.

Posted via WinCustomize Browser/Stardock Central
Reply #2 from WinCustomize Forums Top

It would require the primary to listen for incoming connections, but that sounds like it might work in your case.  The primary remaining stable is obviously key, but in general desktop pcs don't change location so I don't see that as being much of a problem. 

Zubaz: That works ok as long as the lookup of the machine name is reliable.  On some large & busy networks that IP change might not get noticed for 10 minutes or so.

One thing I have wondered about is what happens if you flush the DNS cache from XP.  Does this then make it lookup the correct IP.

The Political Machine 2024