Client DHCP, WIFI and suspend mode...

  • Thread starter Thread starter Will Hughes
  • Start date Start date
W

Will Hughes

Okay, I think this must be a "known issue" but haven't
found anything in the knowledge base or in this newsgroup.

I've got a straightforward network at home. Several
workstations doing tcp/ip and win networking through a
NAT/DHCP/WIFI box (Netgear MR814) with DSL out to that
illustrious Internet people are starting to talk about.
Most of the workstations are hardwired, but my portable is
wifi using a Linksys WPC11v3 card.

The problem: maybe 1 times in 5 upon waking up the laptop
(old Toshiba, but running Win2k, SP4, all recent updates)
and it comes out of suspend mode, I don't get tcp/ip
connectivity. Win networking is fine. If I run
ipconfig/all I see an ip address of 0.0.0.0 and if I try
to stop the dhcp client, it hangs, and so "net stop dhcp"
eventually returns, "unable to stop..."

So this feels like a race error: after returning from
suspend mode, I notice that the client always wants to
renew the dhcp lease. I'm guessing that it tries this as
the wifi card is powering up and hasn't quite connected
yet, so this sends the dhcp client into a tizzy.

I don't have any reason to suspect the DHCP server (the
Netgear MR814) because it's just seemed damned reliable
and haven't heard of anyone on the net having this problem
with it, but maybe it's not playing nice and that is what
is screwing the dhcp client?

The only solution is reboot, which is pretty annoying.

Known bug? Known patch maybe? Or workaround?

Would love to solve this.

TIA,

Will Hughes
 
I would think the problem is the suspend mode. Windows 2K handled it ok, XP
handles it much better. What you might want to do is the following.

Wake the system up.
Once responsive, from a cmd prompt do a
ipconfig /renew
or
ipconfig /release & ipconfig /renew

or disable and then reenable the nic.
Make sure that you are also running ALL the Toshiba specific drivers that
deal with wakeup/suspend. If the system if older, I would honestly think the
root problem is the notebook. Make sense?
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
 
Back
Top