A
aleinss
Hi guys.
Wondering if anyone out there has ran into this issue. We have sales
guys that take their laptops out on the road with them, specifically
these are Dell D600/D610s. Any ways, they bring them back into
corporate and the laptop takes 3 to 4 minutes to bring up the Novell
login screen. During this time there is very little disk activity. If
I disable the onboard wireless card, the laptop boots up very fast to
the Novell login screen. If I check the event log, the laptop is
trying to get a DHCP address from someone's private wireless access
point. Only one person has access to this WAP, so the attempt fails.
Unfortunately, the laptop waits 3 to 4 minutes trying to obtain a DHCP
address from this WAP and times out.
It doesn't matter if it plugged into Ethernet or not. It seems to
want to grab an IP address for the wireless card even if it already has
an Ethernet connection. The interesting thing is that if I clear all
of the wireless profiles out of the laptop and reboot, it boots up
really fast. However, when they go back on the road and start hitting
hotels and other places that host their own WAPs, the sales guys come
back with a bunch of wireless profiles and the process starts all over
again.
I did try updating the drivers, but still happens. This is happening
to all the sales guys with laptops.
Any ideas?
Thanks,
Adam
Wondering if anyone out there has ran into this issue. We have sales
guys that take their laptops out on the road with them, specifically
these are Dell D600/D610s. Any ways, they bring them back into
corporate and the laptop takes 3 to 4 minutes to bring up the Novell
login screen. During this time there is very little disk activity. If
I disable the onboard wireless card, the laptop boots up very fast to
the Novell login screen. If I check the event log, the laptop is
trying to get a DHCP address from someone's private wireless access
point. Only one person has access to this WAP, so the attempt fails.
Unfortunately, the laptop waits 3 to 4 minutes trying to obtain a DHCP
address from this WAP and times out.
It doesn't matter if it plugged into Ethernet or not. It seems to
want to grab an IP address for the wireless card even if it already has
an Ethernet connection. The interesting thing is that if I clear all
of the wireless profiles out of the laptop and reboot, it boots up
really fast. However, when they go back on the road and start hitting
hotels and other places that host their own WAPs, the sales guys come
back with a bunch of wireless profiles and the process starts all over
again.
I did try updating the drivers, but still happens. This is happening
to all the sales guys with laptops.
Any ideas?
Thanks,
Adam