You can read my previous post about this problem here.
I think I found a solution. If it stays for at least a day or two, I think this is it. There are two things you can try on your end if you have this problem of losing the default gateway settings on your multihomed Windows 2003 server.
- Use the route command and use persistent connection.
- Change your dead gateway detection settings.
1. Use the route command and use persistent connection. (This is what I using.)
Most of us have probably use the route command to primarily print the routing table on win xp or windows 2000 or windows 2003. You can also use the route command to add routes to the routing table. Normally adding routes to the routing table are deleted or purged everytime the computer restarts. However if we use the route command with “-p” parameter, you make a route persistent, and will stay as is after reboot.
The syntax for the route command is:
route [-f] [-p] [Command [Destination] [mask Netmask] [Gateway] [metric Metric]] [if Interface]]
to print the routing table, simply use: route print
with regards to our default gateway problem this is what i’m using :
route -p add 0.0.0.0 mask 0.0.0.0 192.168.0.1 metric 1 if 1
2. Change your dead gateway detection settings. (I will try this next, if the first one doesn’t work)
What is a dead gateway detection anyway?
Dead gateway detection allows Transmission Control Protocol (TCP) to detect failure of the default gateway and to adjust the Internet Protocol (IP) routing table to use another default gateway.
For more information about default gateway detection, please click here.
Reg Settings:
System Key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters]
Value Name: EnableDeadGWDetect
Data Type: REG_DWORD (DWORD Value)
Value Data: (0 = false, 1 = true)
If you want to disable this setting, the Value Data should be 0 .
Hope this helps. If any of you comes up with another solution, you can freely post it here for others to see.
sfad