Problem with XP SP2 and DHCP

[Lasse]

Hi

I sometimes encounter a problem with some of our users. They use their
company notebook at home on their own internet connection, when they bring
the notebook back to work they can use our servers, but can't browse the
internet. The problem is that the NIC doesn't renew the users IP addresses,
so if the users private network is the same as the companies except for the
DNS servers everything except for browsing will work.
Why don't XP renew the IP's correctly?

/Lasse

 

[Robert L. \(MS-MVP\)]

Post back with the result of "netsh interface ip show config" 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

 

[GTS]

I run into that problem too. Sometimes it's because they are waking the
laptop from standby or hibernate and if they reboot (or do a real shutdown
instead) it will then receive a proper DHCP assignment.
Occasionally I have made a batch file and desktop icon for the user that
runs an ipconfig /release and then renew to address this.

 

[Lanwench [MVP - Exchange]]

Hi

I sometimes encounter a problem with some of our users. They use their
company notebook at home on their own internet connection, when they
bring the notebook back to work they can use our servers, but can't
browse the internet. The problem is that the NIC doesn't renew the
users IP addresses, so if the users private network is the same as
the companies except for the DNS servers everything except for
browsing will work.
Why don't XP renew the IP's correctly?

/Lasse

Have them shut down their computers before they bring them in to the office,
and boot up there while connected. Or, have them release & renew the IP
address. Or have them repair the network connection (which will release and
renew the IP address).

NB: If you're using the same private IP subnet at work (e.g.,
192.168.1.0/24, 192.168.0.0/24, etc) used by most consumer-grade/home
"routers" then I suggest you change your office network to use something
less common (e.g., I usually use 172.16.x.x/.24). This will fix a lot of
similar problems to yours, as well as allow remote users to access the
network via VPN if you use that.