Avatar of MarkIsrael
MarkIsrael
Flag for United States of America asked on

When DHCP users move between offices the IP address won't change?

We have several District offices each on Frame-Relay with each office on DHCP with their own private 10. IP adress. When "User A1" goes to Office B2" they connect to the LAN/WAN via DHCP. Then when "User A1" retuns to their office they can't connect to the LAN/WAN. The computer won't let go of the other offices IP address. I try IPCONFIG /Release with no luck. I end up hard coding the IP address into the TCP/IP with that offices IP address and it works. Then I remove the hard coded IP Address and they get the DHCP address they need. Whats up with that?
TCP/IPDHCP

Avatar of undefined
Last Comment
jemery27

8/22/2022 - Mon
SOLUTION
youngrmy

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
MarkIsrael

ASKER
Is there a Microsoft KB acknowlegeing the bug? We have tried the removal but so many computers come with the Ethernet card on the motherboard. Setting the computer to a manual IP and logging in and then setting them back to DHCP also works. There is a tool called XPTCPREP.EXE my partner is trying it out and it looks like it works. I would prefer something else than shareware. At least I know it is a bug. http://www.winsite.com/winxp/sysutil/page14.html
ASKER CERTIFIED SOLUTION
jemery27

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
MarkIsrael

ASKER
I will try this and see how it goes. Everything was set to an 5 hours which very well is the bug/culprit. I will see how it works out and get back to you. BTW - I set it to 1 hour but I am worried about increased traffic on the WAN.
SOLUTION
youngrmy

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
SOLUTION
youngrmy

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
jemery27

I don't think a dhcp lease time of 1 hour will cause any network problems. DHCP packets are very small so unless you are sending them over a wan they can hardly have any impact. When the lease is et to 1 hour, every client wil lrefresh it's lease at half the lease duration - so every 30 minutes. Could try it and see if it fixes the problem.

You might also check your subnet masks and routing. Make sure the client cannot contact the old dhcp server from the new network. If they can, then it would be very strange as they might actually get a response that they could go ahead and keep the old address. The lease time would probably fix that, but would be interesting to know the real reason they are keeping the address.

Jason
Your help has saved me hundreds of hours of internet surfing.
fblack61