Dead Gateway Detection

Hello,

I am testing the “dead gateway detection� feature with Windows Server 2003
and unable to get it to work. The feature works fine with Windows XP.

I've tested this feature using several different methods, but the easiest
test is this: Just add a second false gateway to your NIC. Give it a lower
metric so that it will be listed as the default gateway when using the “route
print� command. After a minute or so, the server should automatically switch
from using the false gateway to the working one and connectivity will be
restored.

Has anyone had success with this feature using Windows 2003? If so, how do
you do it?

Scott,
I believe that when 3 out of 4 packets fail the gateway will switch.
Time does not really come into it.
What you need to do is send some traffic out of the default gateway.

"Scott" wrote:

> Hello,
>
> I am testing the “dead gateway detection� feature with Windows Server 2003
> and unable to get it to work. The feature works fine with Windows XP.
>
> I've tested this feature using several different methods, but the easiest
> test is this: Just add a second false gateway to your NIC. Give it a lower
> metric so that it will be listed as the default gateway when using the “route
> print� command. After a minute or so, the server should automatically switch
> from using the false gateway to the working one and connectivity will be
> restored.
>
> Has anyone had success with this feature using Windows 2003? If so, how do
> you do it?
>

Hello,

I'm confident that I meet and exceed the failed packet requirement. Here's
why: I spend 5-10 mins trying to access websites in the browser and PINGing
domain names, but still no switch. My tests generate numerous HTTP requests
and DNS lookups -- all going out the gateway. All of the requests fail and
continue to fail. I do the same tests in Windows XP and the gateway switches
just fine.

I would like someone to test this feature in Windows 2003 and let me know if
it works. I've tried it on several servers already.

Thanks,
Scott

"Wendel Hamilton" wrote:

> Scott,
> I believe that when 3 out of 4 packets fail the gateway will switch.
> Time does not really come into it.
> What you need to do is send some traffic out of the default gateway.
>
> "Scott" wrote:
>
> > Hello,
> >
> > I am testing the “dead gateway detection� feature with Windows Server 2003
> > and unable to get it to work. The feature works fine with Windows XP.
> >
> > I've tested this feature using several different methods, but the easiest
> > test is this: Just add a second false gateway to your NIC. Give it a lower
> > metric so that it will be listed as the default gateway when using the “route
> > print� command. After a minute or so, the server should automatically switch
> > from using the false gateway to the working one and connectivity will be
> > restored.
> >
> > Has anyone had success with this feature using Windows 2003? If so, how do
> > you do it?
> >

It won't switch until the existing Gateway is gone (powered off or cable
unpluged). Then after wards it will *not* switch back automatically when
the original one comes back up again.

These articles go all the way back to NT4,...but nothing is changed worth
mentioning, there have only been minor improvements and I couldn't even name
the improvements if you asked.

128978 - Dead Gateway Detection in TCP/IP for Windows NT
http://support.microsoft.com/default...b;EN-US;128978

171564 - TCP/IP Dead Gateway Detection Algorithm Updated for Windows NT
http://support.microsoft.com/default...b;EN-US;171564


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------





"Scott" <(E-Mail Removed)> wrote in message
news:57E373A6-B708-49D2-9CD1-(E-Mail Removed)...
> Hello,
>
> I'm confident that I meet and exceed the failed packet requirement.
Here's
> why: I spend 5-10 mins trying to access websites in the browser and
PINGing
> domain names, but still no switch. My tests generate numerous HTTP
requests
> and DNS lookups -- all going out the gateway. All of the requests fail
and
> continue to fail. I do the same tests in Windows XP and the gateway
switches
> just fine.
>
> I would like someone to test this feature in Windows 2003 and let me know
if
> it works. I've tried it on several servers already.
>
> Thanks,
> Scott
>
> "Wendel Hamilton" wrote:
>
> > Scott,
> > I believe that when 3 out of 4 packets fail the gateway will switch.
> > Time does not really come into it.
> > What you need to do is send some traffic out of the default gateway.
> >
> > "Scott" wrote:
> >
> > > Hello,
> > >
> > > I am testing the "dead gateway detection" feature with Windows Server
2003
> > > and unable to get it to work. The feature works fine with Windows XP.
> > >
> > > I've tested this feature using several different methods, but the
easiest
> > > test is this: Just add a second false gateway to your NIC. Give it a
lower
> > > metric so that it will be listed as the default gateway when using the
"route
> > > print" command. After a minute or so, the server should automatically
switch
> > > from using the false gateway to the working one and connectivity will
be
> > > restored.
> > >
> > > Has anyone had success with this feature using Windows 2003? If so,
how do
> > > you do it?
> > >

Hello,

There is no documentation that states the gateway needs to be powered off or
disconnected. Rather, dead gateway detection relies on an end-to-end
protocol (such as TCP). A host can switch its default gateway even when the
current default gateway is fully operational. So, only a disruption in
communication is required.

Windows XP switches gateways, Windows 2003 does not. Very strange.

Does anyone have a solution to this problem? It's easy to test this
yourself. See my first post.

Scott

"Phillip Windell" wrote:

> It won't switch until the existing Gateway is gone (powered off or cable
> unpluged). Then after wards it will *not* switch back automatically when
> the original one comes back up again.
>
> These articles go all the way back to NT4,...but nothing is changed worth
> mentioning, there have only been minor improvements and I couldn't even name
> the improvements if you asked.
>
> 128978 - Dead Gateway Detection in TCP/IP for Windows NT
> http://support.microsoft.com/default...b;EN-US;128978
>
> 171564 - TCP/IP Dead Gateway Detection Algorithm Updated for Windows NT
> http://support.microsoft.com/default...b;EN-US;171564
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> "Scott" <(E-Mail Removed)> wrote in message
> news:57E373A6-B708-49D2-9CD1-(E-Mail Removed)...
> > Hello,
> >
> > I'm confident that I meet and exceed the failed packet requirement.
> Here's
> > why: I spend 5-10 mins trying to access websites in the browser and
> PINGing
> > domain names, but still no switch. My tests generate numerous HTTP
> requests
> > and DNS lookups -- all going out the gateway. All of the requests fail
> and
> > continue to fail. I do the same tests in Windows XP and the gateway
> switches
> > just fine.
> >
> > I would like someone to test this feature in Windows 2003 and let me know
> if
> > it works. I've tried it on several servers already.
> >
> > Thanks,
> > Scott
> >
> > "Wendel Hamilton" wrote:
> >
> > > Scott,
> > > I believe that when 3 out of 4 packets fail the gateway will switch.
> > > Time does not really come into it.
> > > What you need to do is send some traffic out of the default gateway.
> > >
> > > "Scott" wrote:
> > >
> > > > Hello,
> > > >
> > > > I am testing the "dead gateway detection" feature with Windows Server
> 2003
> > > > and unable to get it to work. The feature works fine with Windows XP.
> > > >
> > > > I've tested this feature using several different methods, but the
> easiest
> > > > test is this: Just add a second false gateway to your NIC. Give it a
> lower
> > > > metric so that it will be listed as the default gateway when using the
> "route
> > > > print" command. After a minute or so, the server should automatically
> switch
> > > > from using the false gateway to the working one and connectivity will
> be
> > > > restored.
> > > >
> > > > Has anyone had success with this feature using Windows 2003? If so,
> how do
> > > > you do it?
> > > >
>
>
>

"Scott" <(E-Mail Removed)> wrote in message
news:EF479CE8-5FC3-41DA-A7E5-(E-Mail Removed)...
> There is no documentation that states the gateway needs to be powered off
or
> disconnected. Rather, dead gateway detection relies on an end-to-end
> protocol (such as TCP). A host can switch its default gateway even when
the
> current default gateway is fully operational. So, only a disruption in
> communication is required.

Power down the gateway device or unplug the cable (on it , not the PC) and
find out. If it doesn't switch after a while then you do have an
issue,...if it does switch, then I was right.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

Hello,

I did that test and it didn't switch, but I will try it again. Phillip, are
you able to test this feature? I'm beginning to think I'm the only one in
the world who can't get it to work.

Thanks for your help.
Scott

"Phillip Windell" wrote:

> "Scott" <(E-Mail Removed)> wrote in message
> news:EF479CE8-5FC3-41DA-A7E5-(E-Mail Removed)...
> > There is no documentation that states the gateway needs to be powered off
> or
> > disconnected. Rather, dead gateway detection relies on an end-to-end
> > protocol (such as TCP). A host can switch its default gateway even when
> the
> > current default gateway is fully operational. So, only a disruption in
> > communication is required.
>
> Power down the gateway device or unplug the cable (on it , not the PC) and
> find out. If it doesn't switch after a while then you do have an
> issue,...if it does switch, then I was right.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
>
>
>

I don't have an "environment" handy that I can test it in right now. I
guess I could do it in Virtual PC, but it would take a lot of time for me to
rig up. I'm kinda hoping others that might be watching the thread would
have some ideas.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"Scott" <(E-Mail Removed)> wrote in message
news:1E2540F5-F2F6-4C31-BBCE-(E-Mail Removed)...
> Hello,
>
> I did that test and it didn't switch, but I will try it again. Phillip,
are
> you able to test this feature? I'm beginning to think I'm the only one in
> the world who can't get it to work.
>
> Thanks for your help.
> Scott
>
> "Phillip Windell" wrote:
>
> > "Scott" <(E-Mail Removed)> wrote in message
> > news:EF479CE8-5FC3-41DA-A7E5-(E-Mail Removed)...
> > > There is no documentation that states the gateway needs to be powered
off
> > or
> > > disconnected. Rather, dead gateway detection relies on an end-to-end
> > > protocol (such as TCP). A host can switch its default gateway even
when
> > the
> > > current default gateway is fully operational. So, only a disruption
in
> > > communication is required.
> >
> > Power down the gateway device or unplug the cable (on it , not the PC)
and
> > find out. If it doesn't switch after a while then you do have an
> > issue,...if it does switch, then I was right.
> >
> > --
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> > -----------------------------------------------------
> > Understanding the ISA 2004 Access Rule Processing
> > http://www.isaserver.org/articles/IS...cessRules.html
> >
> > Microsoft Internet Security & Acceleration Server: Guidance
> > http://www.microsoft.com/isaserver/t...dance/2004.asp
> > http://www.microsoft.com/isaserver/t...dance/2000.asp
> >
> > Microsoft Internet Security & Acceleration Server: Partners
> > http://www.microsoft.com/isaserver/partners/default.asp
> > -----------------------------------------------------
> >
> >
> >
> >
> >

I presume you know about this (mskb 324270):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es

Value name: EnableDeadGWDetect
Key: Tcpip\Parameters
Value Type: REG_DWORD
Valid Range: 0, 1 (False, True)
Default: 1 (True)

The following list explains the parameters that you can use with this
registry value:
.. 1: When you set EnableDeadGWDetect to 1, TCP is permitted to perform
dead-gateway detection. When dead-gateway detection is enabled, TCP may ask
the Internet Protocol (IP) to change to a backup gateway if a number of
connections are experiencing difficulty. Backup gateways are defined in the
Advanced section of the TCP/IP configuration dialog box in the Network tool
in Control Panel.
.. 0: Microsoft recommends that you set the EnableDeadGWDetect value to 0. If
you do not set this value to 0, an attack may force the server to switch
gateways and cause it to switch to an unintended gateway.


"Phillip Windell" <@.> wrote in message
news:%23$(E-Mail Removed)...
>I don't have an "environment" handy that I can test it in right now. I
> guess I could do it in Virtual PC, but it would take a lot of time for me
> to
> rig up. I'm kinda hoping others that might be watching the thread would
> have some ideas.
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
> "Scott" <(E-Mail Removed)> wrote in message
> news:1E2540F5-F2F6-4C31-BBCE-(E-Mail Removed)...
>> Hello,
>>
>> I did that test and it didn't switch, but I will try it again. Phillip,
> are
>> you able to test this feature? I'm beginning to think I'm the only one
>> in
>> the world who can't get it to work.
>>
>> Thanks for your help.
>> Scott
>>
>> "Phillip Windell" wrote:
>>
>> > "Scott" <(E-Mail Removed)> wrote in message
>> > news:EF479CE8-5FC3-41DA-A7E5-(E-Mail Removed)...
>> > > There is no documentation that states the gateway needs to be powered
> off
>> > or
>> > > disconnected. Rather, dead gateway detection relies on an end-to-end
>> > > protocol (such as TCP). A host can switch its default gateway even
> when
>> > the
>> > > current default gateway is fully operational. So, only a disruption
> in
>> > > communication is required.
>> >
>> > Power down the gateway device or unplug the cable (on it , not the PC)
> and
>> > find out. If it doesn't switch after a while then you do have an
>> > issue,...if it does switch, then I was right.
>> >
>> > --
>> > Phillip Windell [MCP, MVP, CCNA]
>> > www.wandtv.com
>> > -----------------------------------------------------
>> > Understanding the ISA 2004 Access Rule Processing
>> > http://www.isaserver.org/articles/IS...cessRules.html
>> >
>> > Microsoft Internet Security & Acceleration Server: Guidance
>> > http://www.microsoft.com/isaserver/t...dance/2004.asp
>> > http://www.microsoft.com/isaserver/t...dance/2000.asp
>> >
>> > Microsoft Internet Security & Acceleration Server: Partners
>> > http://www.microsoft.com/isaserver/partners/default.asp
>> > -----------------------------------------------------
>> >
>> >
>> >
>> >
>> >
>
>