Sunday, January 13, 2013 8:53 PM
I have a TMG 2010 server using ISP Failover.
The Primary ISP is a Cable Modem connection and is configured for Dynamic IP Address (DHCP).
The Secondary ISP is a DSL connection with Static IP Addresses.
Due to an extended Cable Modem outage, our external IP Address on the Cable Modem connection changed. I now have a new IP Address to the ISP at that network adapter, which I can monitor using a packet sniffer and see using ipconfig. However, the TMG 2010 Port 53 packets are not being sent out the restored connection and TMG is not reverting back to that connection.
I went to the Forefront TMG Networking Menu and then clicked on the ISP Redundancy tab. I noticed that the properties of the Cable Modem connection still showed the old IP address. I modified the properties and entered the new IP Address and applied the changes. Still no port 53 test on the Cable Modem connection.
I then disabled and re-enabled the physical adapter in Microsoft Windows. Still no port 53 test.
What other items can be tried to get the TMG 2010 to revert back to the Cable Modem with this new IP Address? Restarting the server may be a fix, but I am trying to find a solution that will not require the interruption of the traffic on the Secondary ISP.
Gibson Teldata, Inc.
Tuesday, January 15, 2013 2:19 PMModerator
Thank you for the post.
“What other items can be tried to get the TMG 2010 to revert back to the Cable Modem with this new IP Address?” – you may apply the following actions on TMG server to reset TCP/IP stack before restarting the server:
netsh winsock reset
netsh int ip reset
Nick Gu - MSFT
- Proposed As Answer by Nick Gu - MSFTMicrosoft Contingent Staff, Moderator Saturday, January 19, 2013 3:07 PM
Saturday, January 19, 2013 9:33 PM
Well, this was not what I was looking for. I am looking for a way to use the newly assigned address on the Primary ISP Interface without re-booting. The commands above required a re-boot. In addition, they cleared all of the IP Address settings for all of the external and internal network adapters.
The only solution I have found is to manually change the information in the Networking Menu, ISP Redundancy tab for the network connection to the correct numbering scheme and then remove and re-install the ISP Failover feature. This may cause a brief interruption of service to the people that had already failed over to the secondary connection, but it wasnt enough to create a noticeable issue.