I had a similar problem a few years ago when I first switched from Road Runner to Verizon FiOS. The laptop hosting the feed would lose its ability to talk to the router after an ISP-forced IP change like you described and that ultimately prevented the feed software from reconnecting to LiveATC's servers.
To get around this I wrote a small batch script that would ping the router's IP address and if an error code were returned, the script would reboot the laptop. After rebooting, the feed software was able to reconnect to the Live ATC servers. I then attached this script to a more robust, free Windows scheduler that I found and the script ran every 15 minutes every day. This script kept my feed up throughout the day when I was traveling.
In my case, though, I eventually upgraded routers and Verizon FiOS switched to DHCP so the script was no longer needed (although I do have a script that reboots the laptop once every two weeks late Sunday night just to clean up Windows).
If you are interested in the ping/reboot script and the link to this more robust Windows scheduler, I posted them both to this thread here back in 2006:
http://www.liveatc.net/forums/index.php/topic,1409.0.htmlAlso, if you haven't seen my recent post about the free remote desktop solution in the Feeders forum, there is a free, remote Windows desktop utility called LogMeIn Free that will allow you to remotely connect to your feed computer while on the road, assuming Windows did not crash or there is an interruption in your home computer's Internet connectivity. I have been using this utility to manage my feed since I am on the road four days a week and it works very well. That utility can be found here:
https://secure.logmein.com/products/free/Good luck,