Does anyone know how to change the dropped network connection timeout on a
host PC so that when I’m debugging the target with Windbg my network
connection isn’t dropped?
I have a target PC that runs an application from a network drive. When I
break in with Windbg, if I stay in the debugger for more than a minute the
application crashes with an in-page error as soon as I resume execution.
This used to work fine on NT, got a little worse with 2000 and is terrible
now that the host is running XP.
Has anyone else experienced this problem and found a workaround (other than
copying the application to the target)? I suspect that one of the network
timeout values in the registry might do the trick but which one?
Just a guess, but it could be that freezing the target fools Windows’ “media sense” feature into believing that the net link is down. To find out, try disabling media sense, per this KB article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q239924
As the article says, you will still see the “network disconnected” icon with media sense disabled, but the TCP stack ignores that.
– Chris
----- Original Message -----
From: Whitman, Steve
To: Kernel Debugging Interest List
Sent: Friday, May 17, 2002 3:10 PM
Subject: [windbg] Network connections dropped
Does anyone know how to change the dropped network connection timeout on a
host PC so that when I’m debugging the target with Windbg my network
connection isn’t dropped?
I have a target PC that runs an application from a network drive. When I
break in with Windbg, if I stay in the debugger for more than a minute the
application crashes with an in-page error as soon as I resume execution.
This used to work fine on NT, got a little worse with 2000 and is terrible
now that the host is running XP.
Has anyone else experienced this problem and found a workaround (other than
copying the application to the target)? I suspect that one of the network
timeout values in the registry might do the trick but which one?