Hi All,

I'm having exactly the same problem described in August in: http://computing.net/networking/wwwboard/forum/21800.html. None of the ideas suggested there seem to work. Does anyone have further things to try?

Pertinent description of the problem (mainly pasted from the other thread):

Suspended laptop at work on wireless LAN w/ DHCP assigned address. Came home, woke it back up on my home wireless LAN. The wireless ip would be put at 0.0.0.0 and not connect. With a wired connection it works fine. I figure this is an issue with the dhcp not properly setting it. The status of the connection shows packets being sent but none being received. When I manually configure it by putting in the ip address, gateway address, and dns servers I found from the working wired connection it works.

The ipconfig renew and release has been tried and did not work. ipconfig /renew tells me something like "unable to access the adapter". The interesting thing is if I use an ethernet cable from the same router it works fine, as does the manual configuration. Even more suspiciously, I have another computer on the network connected wirelessly and running smoothly. So it would seem that the dhcp server works, as it's working for one computer, but something with my particular computer is preventing it from working properly. In the event log I've gotten event id 1002 every 2 seconds it seems. It says The IP address lease 0.0.0.0 for the Network Card with network address <> has been denied by the DHCP server 192.168.1.1 (The DHCP Server sent a DHCPNACK message). Does any of this give any new ideas?

btw- this is on a Linksys wireless AP + router.

thanks
Tony

Did you look at the list of available networks, and choose the home network when you get home??

Yes - I'm automatically connected to my home wireless access point. I've confirmed that, and I have a unique SSID and am using WEP security.

Any other ideas out there...?

strangely enough I had a similar issue on my network at home. It was actually a wired connection hooked to an actiontec wireless DSL gateway which had NAT and DHCP built in among other things and kept trying to find web sites at ip 0.0.0.0 consistantly after leaving the connection idle for a few minutes.
The solution I found to this problem was to set up my computer with a static IP address to the same IP that the gateway usually assigned to it. Basically my gateway would always assign 192.168.0.2 using DHCP, so I set static IP to that same ip, and for the DNS server entered the actual DNS IP's for my ISP. (too many acronyms. . .sorry, hope you can understand all of that mess) My point is that once I started using the static IP setting on the computer itself with the correct dns settings everything worked beautifully. Even nicer is that I didn't even have to set up static routing and left DHCP on the gateway since I set the same ip the gateway assigns anyways.
It was the only solution I found since all my other computers on the network (win98, 2000, linux, etc) connected just fine, for some reason XP just had issues.
I highly suggest setting the IP of your computer to that which your network assigns to it when it does assign one, I know it sounds goofy but like I said it worked fine for me and it's the only solution myself and the tech support lady I was on the phone with for about an hour found. Let me know if it doesn't work, I have a few other tricks up my sleeve. . .