Two interfaces, but WinXP DNS service continues to use DNS entries for disconnected/disabled interfa

[frnkblk]

I have a customer who uses their laptop both at work and home. For
work they have a statically entered NATed IP address (172.x.x.x),
subnet mask, gateway, and DNS servers on their wired interface.

At home, they have a NATed wireless connection with DHCP, but on a
different private subnet (192.168.1.x) than the one at work. When I
used ipconfig I see that all the information is correct, but browsing
the web fails. Using nslookup we learned that DNS lookups continue to
work off the wired interface, even though that interface is
disconnected. Disabling the wired interface doesn't help. To clarify,
"running ipconfig /all" at the customer's home does not show any of the
statically entered DNS servers for the wired interface.

I'm mystified why WinXP continues to use the wired interface's
statically entered DNS settings even though that interface is down.
Any ideas?

Frank

 

[Robert L [MVP - Networking]]

posting the result of ipconfig /all here may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I have a customer who uses their laptop both at work and home. For
work they have a statically entered NATed IP address (172.x.x.x),
subnet mask, gateway, and DNS servers on their wired interface.

At home, they have a NATed wireless connection with DHCP, but on a
different private subnet (192.168.1.x) than the one at work. When I
used ipconfig I see that all the information is correct, but browsing
the web fails. Using nslookup we learned that DNS lookups continue to
work off the wired interface, even though that interface is
disconnected. Disabling the wired interface doesn't help. To clarify,
"running ipconfig /all" at the customer's home does not show any of the
statically entered DNS servers for the wired interface.

I'm mystified why WinXP continues to use the wired interface's
statically entered DNS settings even though that interface is down.
Any ideas?

Frank

 

[frnkblk]

I don't have access to that machine right now, but 'ipconfig /all'
shows the wired adapter as disconnected, and the wireless lists the
wireless router's IP address as the DHCP server and gateway, and of
course assigns the correct IP address and DNS servers. Yet browsing
the web with DNS names fails, and I can confirm the browsers problems
by running nslookup, which pulls up a reference to a DNS server of
172.x.x.x. which resides at the customer's work site.

So, any more ideas where WinXP is storing this 172.x.x.x IP address and
superseding the ones that were handed out via DHCP?

Frank