[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 200
  • Last Modified:

XP won't communicate with new DHCP server

I've been having problems with my XP computers in my small office network when they move from one network/subnet and DHCP server to another.  If I connect a computer using DHCP to one network, then move it to the other network, I can connect, but it won't pull down an IP.  I keep getting "DHCP server unavailable" when I run ipconfig /release and ipconfig /renew.  The "repair" option in the GUI doesn't work either.  It's as if windows XP doesn't realize that there is a new DHCP server on the network.  It insists on trying to renew an address in the old address range.  

I've also tried "netsh int ip reset" in hopes that it would reset some setting that ties a particular network interface to a DHCP server or address range.

I've had this problem on 4 laptops now.  My workaround has just been to only connect wirelessly to one of the networks, that way I never have to renew an IP in a new subnet and with a new DHCP server.  In one instance, I actually had to swap out the wireless network card with another to get windows to connect happily to a new wireless network.

I've heard from other IT friends that this is a common windows XP problem but I haven't been able to find an elegant solution online (ie: something other than changing hardware or reinstalling the OS).  


0
bjulian
Asked:
bjulian
1 Solution
 
SysExpertCommented:
You might look into a third party IP program like netswitcher.

Some laptops 9 IBM etc ) may have something like this already installed.

I hope this helps !

0
 
sparkofgeniusCommented:
have you tried simply statically assigning the ips?

this way they have no need to go through your dhcp server. its not ideal but it is as you say a common xp problem.
0
 
bjulianAuthor Commented:
Static addresses work but I'd rather not do that because I'd have to reserve each IP, or assign addresses outside of the DHCP address pool.
0
 
bjulianAuthor Commented:
I think it was a hardware problem after all, and not an issue with XP this time.   I replaced a cable and it started working.  I would have expected either a fully functional connection or no connection, but apparently wierd things can happen with a degraded network connection.
0
 
Computer101Commented:
PAQed with points refunded (250)

Computer101
EE Admin
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now