"Acquiring network address", then "Limited or no connectivity"

HC_2

... on a desktop running XP, connected wirelessly to a Netgear router by way of a Netgear WPN111 adapter.

It suddenly stopped working. This is not the first time, but this time nothing I do will make it connect again.

I've Googled the problem and done everything possible that I can see, including:

• Rebooting
• Restarting WZC and DCHP client
• Unplugging and then reconnecting the wireless adapter
• Clicking 'Repair'
• Using IE's diagnostic tool
• Deleting the network in network list and letting it refind it
• Turning off my firewall
• Opening cmd and typing ipconfig/release and /renew
• Opening cmd and typing netsh int ip reset resetlog.txt and then netsh winsock reset catalog
• Opening cmd and typing ipconfig/flushdns
• Assigning manual IP and DNS addresses (this gives me a false connection)
• Rebooting the router
• Turning off, and then turning back on the router
• Changing the default to Enable NetBios over TCP/IP
• Uninstalling and reinstalling the Netgear network adapter
• Running Wireless Network Wizard (that solved the problem for someone, but not me)

I have a laptop (the one I'm on now) that is wirelessly connected perfectly, and which rarely falls over.

Does anyone have any suggestions that I haven't tried?

Thank you.

netdumdum

I have the same adapter and they can be tempermental, however it looks like you have done everything that I would have suggested.

I think me writing this post was a waste of time, good luck anyway, sorry cant help!

tomstickland

This reminds me of problems I had with wireless networking.
Running ipconfig -renew in a DOS window helped quite a lot.
It also pays to make sure that you don't have more than 1 program trying to manage any connections.

HC_2

netdumdum wrote: »

I have the same adapter and they can be tempermental, however it looks like you have done everything that I would have suggested.

I think me writing this post was a waste of time, good luck anyway, sorry cant help!

:rotfl:

Temperamental isn't the word!

I've just checked Device Manager and the adapter is working properly.

Allegedly.

HC_2

tomstickland wrote: »

This reminds me of problems I had with wireless networking.
Running ipconfig -renew in a DOS window helped quite a lot.
It also pays to make sure that you don't have more than 1 program trying to manage any connections.

What drives me really insane is that it works fine one minute and then falls over for no reason, waving its legs feebly in the air.

If no one can help, tomorrow I shall ring Netgear. They will treat me as though I have never used a computer before, and tell me to check the most ridiculous things.

Then they'll make me go to the router and rename the network, letting the PC find it again, which means I shall have to spend a few hours getting my range extenders to recognise the new network, otherwise the signal on the desktop and this laptop will be pants.

This is 2008 yet we still have to suffer dentistry, invasive gynaecology and - worst of all - WIRELESS NETWORKING...

netdumdum

I cant help thinking that it could be a problem with the router, have you tried installing a different version of the firmware??

Maybe its to do with the adapters driver??

HC_2

netdumdum wrote: »

I cant help thinking that it could be a problem with the router, have you tried installing a different version of the firmware??

Maybe its to do with the adapters driver??

It could be to do with the router, but:

1. the laptop I'm now typing on works perfectly
2. I've rebooted the router
3. I've disconnected and reconnected the router

With regard to the adapter's driver, I've downloaded the most up-to-date driver from the Netgear website, uninstalled the existing driver, and reinstalled from scratch.

The problem appears to be that the PC cannot renew the IP address. The adapter is connected to the network with a lovely strong signal.

I think it'll need a real super-techie MSE PC expert guru of fabulousness to help with this one.

Is anyone up to it? Please...

netdumdum

I am afraid I can only think of two possible solutions,

1, Use system restore to restore the pc to a time it could renew the ip address.

2, Try using a different adapter, that way you know the problem lies with the router.

Woby_Tide

what happens if you connect via ethernet to the router using teh desktop? will it still not assign an IP?

HC_2

netdumdum wrote: »

I am afraid I can only think of two possible solutions,

1, Use system restore to restore the pc to a time it could renew the ip address.

2, Try using a different adapter, that way you know the problem lies with the router.

It did occur to me to do a system restore. I'm not convinced it'll do the trick.

The Netgear adapter is fairly new. The previous incumbent was a Belkin one, which fell over regularly. I threw it into the Thames, going, 'Ha!" and bought a Netgear one. It seems that the problem doesn't lie with the adpater though, since the Netgear one also falls over.

banger9365

have you had a update in windows that mite have do it ,???/