Thanks. I ended up running a system restore and the problem was fixed. I really wish I saw your post before I restored it though. Would have been nice to see those fix options in action.
I have been having connection issues for weeks now and they seem to have finally resolved with this little piece of advice! I've literally devoted hours to trying to solve this puzzle--including phone calls with my ISP, bringing a technician from my ISP out to my house, dropping my laptop off with an IT person at my school, and phone calls with a Dell technical support rep. It would be great if this information were added to the knowledge base that the technical support guys work from if they hear key words from their customers involving issues with adware/spyware removal. At any rate, you have one very happy customer on your hands here! I only wish I could have found these programs packaged with the adware removal programs that I've tried.
It is reported that in XP SP2, the command
netsh winsock reset catalog will fix this problem without the need for these programs. I don't know if anyone's tried that instead of the proven "WinsockXPFix" and "lspfix".
I haven't had the problem in a long time. It occurred on one of my Optiplex machines when I updated a driver for the Linksys wireless card. All I could get was Network Transport not Available whenever I tried to fix things. I could ping and other computers on the LAN could see the Optiplex, but it couldn't see anything else. The first time it happened, I restored from a restore point and solved it. The next time I used WinSockXPFix and solved it. The netsh command didn't work either time.
volcano11
2 Intern
•
28K Posts
0
November 9th, 2004 19:00
First try running winsockfix for XP from the following site:
http://www.spychecker.com/program/winsockxpfix.html
If that doesn't work, try lspfix from the following site:
http://www.cexx.org/lspfix.htm
Steve
antoniolr_00
2 Posts
0
November 10th, 2004 01:00
mel1rose
1 Message
0
November 15th, 2004 02:00
schmieg
335 Posts
0
November 15th, 2004 03:00
jwatt
4.4K Posts
0
November 15th, 2004 18:00
It is reported that in XP SP2, the command netsh winsock reset catalog will fix this problem without the need for these programs. I don't know if anyone's tried that instead of the proven "WinsockXPFix" and "lspfix".
Jim
schmieg
335 Posts
0
November 15th, 2004 18:00