Question Locked

Wireless Internet only works after reinstalling driver; quits after reboot

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a new Dell Latitude D620 laptop that shipped with Vista. Didn't like Vista because it was too slow, so I wiped the drive and installed XP from scratch. Installed drivers for XP from the Dell website, and everything was going well. The last action I remember taking was applying some additional patches that Windows Auto Updated wanted me to apply. After that reboot, I could not connect to the internet through my wireless connection. I can still get on my domain and have full access to the network, but no internet.

*Tried doing a system restore. Tried both to the previous install, and to the previous day. Neither fixed the problem.

*Tried uninstalling the Dell Wireless Utility (and thus the drivers). Reboot. Install Dell Wireless Utility for the 1390 mini-card. Reboot. Wireless internet and networking work great! However, after a single reboot (not making ANY changes to ANYTHING) I'm back to square one.

I've checked my firewall settings, I have it set to automatically obtain IP address from the server (which obviously is working since I can still work on the domain). Connection made is fine, WEP key is accepted, everything! Just no internet.

I've searched high and low online (btw, my wired connection works perfectly on this same laptop) but can't find anything specific to my problem. I doubt it's laptop specific, or NIC specific as I've used these combinations before without issue. Short of starting over again, does anyone have suggestions as to what this could be? Thanks in advance.

5 replies

by bit - twiddler

I've used all of the following with great success, but I would personally prefer to do just a little more troubleshooting, and trying to pinpoint the actual issue here before pulling out the big guns listed below.

1) What does loopback ping yield on the Wifi NIC?

From a command prompt, "ping 127.0.0.1"

If you get 4 packets sent and 4 recieved (0% loss) then the WiFi NIC "seems" ok, which also can be verified via device manager.

2) what does "ipconfig /renew" yield on the buggy wifi?

Different errors(if any) can point to the real solution.

3)Have seen some flaky stuff when using both Wifi and Ethernet...XP gets a little snippy when border-crossing all the time.
some things I have found helpful are:

============================
Try repairing winsock

There a couple of new "Netsh" commands in Windows XP Service Pack 2.

Try:
"netsh winsock reset catalog"
This command resets the Winsock catalog to the default configuration. This can be useful if a malformed LSP is installed that results in loss of network connectivity. While use of this command can restore network connectivity, it should be used with care because any previously-installed LSPs will need to be re-installed (Google desktop search is one I know).

"netsh winsock show catalog"
This command displays the list of Winsock LSPs that are installed on the computer.
NOTE: Do this one FIRST, and output to a text file - IE:
"netsh winsock show catalog >C:\Mylsp.txt"

This will give you an idea of what you have and any that will need to be replaced.
============================
Then actually try to repair the winsock:

http://support.microsoft.com/?kbid=811259

============================
If that STILL doesnt resolve, I've also had some luck with repairing TCP/IP stack:

http://support.microsoft.com/?kbid=299357

============================

Usually the ipconfig /release and /renew will point you in the right direction.

Note: To do all of the above would take about 15 minutes start to finish, so is not a big investment in time.

Also have heard of some conflicts between the ethernet NIC and the Wifi NIC which will fight for control, thus knocking you off the net in 15 minute(?) intervals...I had a link, but now I cannot seem to find it, relative to disabling this "feature" in windows via the registry.

Also while I do not recommend it, I have seen where the WEP key can cause some issues, have you tried it without security enabled?(just as a test)

Hope this helps!

by sinecure

Troubleshooting:

1) Loopback shows 0% loss.

2) ipconfig /renew completes sucessfully, giving an IP address within the DHCP scope.

3) Have tried both with and without the wired NIC enabled. Booted both ways as well.

"netsh winsock show catalog" showed a long list of stuff. Not sure what any of it was.

Did the reset catalog, and it did not make any difference.

The strangest thing is that I turned it on today after it not working yesterday and it worked... the first boot. After a reboot I could not get it to work again.

Also, I took the laptop home over the weekend and it connected flawlessly to my LinkSys WAP. I even rebooted about 5 times to make sure it wasn't a fluke. And I am using a WEP key at home. Brought it back to work on Monday and once again, it worked great upon first booting. After the reboot it quit. Thinking now that it could have something to do with the type of WAP (we use Buffalo), I brought the laptop into a different department which has a LinkSys router, but is on the same network (same WEP key). Much to my dismay, it did not work. So it does not seem to be a router brand issue.

At this point I am seriously stumped. I'm almost totally convinced it is a Windows Update patch that made things go bad. About a month ago, almost this exact same thing happened to me at home. I was reformatting a homebuilt PC that only had a Wireless PCI card in it. After about the same level of applying updates, Internet quit, but I still had a connection to the router. I removed the wireless card and installed a wired ethernet card, and it still didn't work. After a few days of playing with it, I gave up and reformatted again. No problems on the 2nd try.

So I'd almost think that there is an issue with some Windows patches (if that's even the cause), but Microsoft doesn't document anything related to it.

by dazzlin_dazz

Sorry to butt in but I have a similar problem.
I have a HP 510 laptop and I use it when I am at my folks house to connect to the internet (I work away from home so I am often camping out at my folks).
I can connect my laptop to my folks wireless network and at first it works ok but after a while it no longer accesses the internet. The laptop is still connected to the router but no access to the internet.
When I ping the router (192.168.0.1) I get anything from 100% loss, to 25% loss to all ok and some of the pings come back "Request timed out" or "Hardware error".
I have tried re-setting my TCP/IP stack and winsock reset catalog and both times it seems to work initially but after a while (10 mins or so) I start to get the problem back until eventually I have to disconnect from the router and re-connect again.
I have Avast Anti-virus installed and have run a thorough scan with no problems, I have also run a windows defender scan and that also came back clean.

I?m banging my head against a wall here, please can anyone help??

by sgt_shultz

...i put my money on misconfigured gateway.
i am just guessing tho

This discussion is closed to new replies.