Limited or No Connectivity WinXP SP2 Bug

**RedGTiVR6** · 01-27-2005, 07:20 AM

Originally Posted by marley1

its not a serious problem.

it happens because the network card doesn't acquire the full network address usually or it cna be caused from spyware.

Usually you can fix it quick by right clicking on the network connection and clicking repair. if that doens't get it their is something called VBSockFix which will get it all.

again, not true, the computers we have at work have NO spyware when we get them, this even happens to comuters that we put a new image on, which we know is 100% free of spyware.....

but I will be looking into the VBSockFix for sure though!

**marley1** · 01-27-2005, 07:36 AM

its located here

http://www.spychecker.com/program/winsockxpfix.html

i didn't say it was only caused by spyware, its caused sometimes by that, other times when it doesn't grba a full netwrok address.

usually repairing the connection will do it.

**RedGTiVR6** · 01-27-2005, 08:20 AM

repairing the connection has never worked for us in this instance.....usually just letting it sit for a bit repairs it better than anything....lol

**marley1** · 01-27-2005, 09:26 AM

so repairing and letting sit or running the socket fix is the same thing.

lettting it sit gives it more time to repair itself or acquire a new ip/dns...

i hav ehte problem alot when im working on clients computer, plugging em in fast to our switches and kvm at work sometimes doesn't get em to connect right away.

generally i have to either repair the connection, assign manual ip if im too lazy to reall fix it(or when im just gonna be formatting it anyway and need to just backup a few things), releasing the sockets(socketfix) or when i restart.

it can be caused by others, there is the known bug for it but i dont really consider it a bug

**bd3521** · 01-29-2005, 01:21 AM

This is a very annoying bug. I work with quite a few desktops and laptops on a daily basis (all different), and many of them experience these issues. Usually if I disable/re-enable it in device manager it will work (60%). Im working on a fix though...

**bd3521** · 01-30-2005, 01:12 AM

Figured out the solution.
If you need it let me know

**Laidback** · 01-30-2005, 03:28 AM

Originally Posted by bd3521

Figured out the solution.
If you need it let me know

Go on, tell us.

**Bravellir** · 01-30-2005, 05:50 AM

Only got that problem once, and it had something to do with a onboard NIC. ( drivers I gess) Just installed another NIC and the problem disapeared.

**RedGTiVR6** · 01-30-2005, 09:10 AM

lol - bd - you must want to feel important.....heheheh

so what's the solution?

**marley1** · 01-30-2005, 10:50 AM

i have already given the fix to the bug.

it doesn't happen all that offiec, will only happen when first plugging in or if the network dies down.

i guess no one has tried the SockFix. because not onlyt does it fix that but it also fixes alot of spyware infections to the host file.