Network / DHCP
Client network is running W2K3 AD domain with multiple (4) subnets.
One of the users has XP Pro SP2 on his laptop pc (HP nc6400) and travels between sites. He is able to "consistently" obtain a DHCP address from 3 of the sites without any problems. He intermittently has problems obtaining a DHCP address from the 4th site. Some days he gets a DHCP address with no problems and on other days he can not pick up an address.
The problem subnet has a sufficient number of ip addresses available in the pool and all other users at the site do not experience the problem. I have connected his pc to different ports on the switch and still could not get an address. A virus scan of his pc using TM Officescan does not detect any malware or viruses. Ipconfig /release /renew / has no effect. The activity and link light on the nic are normal.
Any ideas on what could be causing the problem or what I can check on his pc?
Thanks,
Cliff
All Replies
- Hello Cliff,
tough one, i would have thought all the IP's in the pool where leased. but you mentioned checking this.
I would check out the event logs, system and security just after connecting the laptop to the 4th subnet and not being able to get an IP.
I would also try running a free and handy ap called TCP/IP Repair
http://www.xp-smoker.com/freeware.html
copy and paste the results of "ipconfig /all" would also be handy to see if he is picking up any information from the router.
Hope this helps. - Thanks for the reply.
I'll give the TCP/IP repair a try.
ipconfig /all shows absolutely nothing.
When the user plugs in his laptop and turns it on, he is able to login using his cached credentials. Once the desktop appears, the local area connection in the system tray says it's acquiring an address but never does.
I can disconnect a known working pc, connect the problem laptop and get the same results.
The week of 24 - 28 Aug. the user was able to connect with no problems on Monday, then experienced the problem again on Wednesday.
The subnet in question always has 25 free addresses at a minimum due to the limited number of users at the site.
Cliff Well I finally figured out what the problem was.
The client has an F5 Networks SSL VPN appliance.
Whenever the user accessed the network via the VPN, he was unable to obtain a DHCP address the following day when physically connected to the network.
It turns out he was closing his browser windows by clicking on the red close button in the upper right corner of IE instead of following the prompts to terminate his session and then closing IE.
Now that he terminates his VPN session and closes IE afterwards, he's not had the problem since.
