Augustus Lowell
January 10th 04, 01:14 AM
I've got a LAN behind two routers/firewalls, with a
"semi-public" (eg. mail server) section between them, and
my private stuff behind the inner one. The outer router is
a LinkSys BEFSR41, which is doing NAT between the external
IP address and my private address range; the inner one is a
SonicWall Tele3 which just provides a firewall between the
two segments -- no NAT.
This has worked fine for years with NT machines, but when I
put a new laptop running XP on it last summer, it kept
spuriously popping up messages asking for a password to log
onto the LinkSys (it has a browser-based configuration
interface) -- as if it were trying to address the router
directly. It didn't behave that way at work, where there
is only a single router between the LAN and the outside.
After a while, despite the fact that I couldn't figure out
what it was doing, it just stopped doing it.
Unfortunately, this summer I upgraded some other computers
to XP, and suddenly the behavior is back -- not just on the
new desktop computers, but also on the laptop which had
been working fine for months. It got so bad that I'd have
to cancel the request 20 times or more for a simple
operation (like "Windows Update").
Following some advice from the web (and in desperation), I
disabled the XP "Internet Gateway Device Discovery" module.
After that the laptop no longer does this, but the desktop
machines still do -- so something changed on the laptop,
but that wasn't it.
Has anyone else seen this? Has anyone figured out what to
do about it?
Thanks.
-apl
"semi-public" (eg. mail server) section between them, and
my private stuff behind the inner one. The outer router is
a LinkSys BEFSR41, which is doing NAT between the external
IP address and my private address range; the inner one is a
SonicWall Tele3 which just provides a firewall between the
two segments -- no NAT.
This has worked fine for years with NT machines, but when I
put a new laptop running XP on it last summer, it kept
spuriously popping up messages asking for a password to log
onto the LinkSys (it has a browser-based configuration
interface) -- as if it were trying to address the router
directly. It didn't behave that way at work, where there
is only a single router between the LAN and the outside.
After a while, despite the fact that I couldn't figure out
what it was doing, it just stopped doing it.
Unfortunately, this summer I upgraded some other computers
to XP, and suddenly the behavior is back -- not just on the
new desktop computers, but also on the laptop which had
been working fine for months. It got so bad that I'd have
to cancel the request 20 times or more for a simple
operation (like "Windows Update").
Following some advice from the web (and in desperation), I
disabled the XP "Internet Gateway Device Discovery" module.
After that the laptop no longer does this, but the desktop
machines still do -- so something changed on the laptop,
but that wasn't it.
Has anyone else seen this? Has anyone figured out what to
do about it?
Thanks.
-apl