[debbieu]

We have a home network of only 2 computers and a printer. Windows XP Home Addition is hooked up to the linksys. The 2nd computer on the connection is a windows vista with a wireless hookup. The xp had a virus so we restored the system. Now the network connection is lost. I would appreciate your help!
Thank you.

[GeekGlobalDotCom]

What do you mean by restored? System restore or reinstall the windows?

[debbieu]

system restore

[GeekGlobalDotCom]

I think the first thing you should do is undo the restore. Viruses may not be able to start due to the restore but they are still there regardless of the restore. Combat the virus issues without restoring the system. You could try winsockfixxp (google) but I think undoing the restore would be the best course of action. System restore should be used to recover registry damage no combat viruses.

[debbieu]

okay, sorry, it wasn't a virus, we had mcaffee take it off remotely, I believe it was malware. Anyways, we had a computer guy come over and that is what he suggested doing. Any other suggestions for networking the computers without undoing the restore?

[GeekGlobalDotCom]

winsokfixxp may do it or it may be registry related outside of the scope of winsock and you may be forced to undo the restore to get the proper registry information back. winsockfixxp is here http://majorgeeks.com/WinSock_XP_Fix_d4372.html also is this wired or wireless connection from the xp to the linksys? please post they output of the command ipconfig /all

[JohnWill]

Actually, the WINSOCK fix mentioned is the incorrect way for XP SP2 or later. If you want the proper fix, it's built-in to XP.


TCP/IP stack repair options for use with Windows XP with SP2/SP3.

Start, Run, CMD to open a command prompt:

In the command prompt window that opens, type type the following commands:

Note: Type only the text in bold for the following commands.

Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog

Reboot the machine.

[GeekGlobalDotCom]

Originally Posted by JohnWill

Actually, the WINSOCK fix mentioned is the incorrect way for XP SP2 or later. If you want the proper fix, it's built-in to XP.


TCP/IP stack repair options for use with Windows XP with SP2/SP3.

Start, Run, CMD to open a command prompt:

In the command prompt window that opens, type type the following commands:

Note: Type only the text in bold for the following commands.

Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog

Reboot the machine.

Funny I never had an issue using it on any XP systems sp1,2 , or 3 guess I learned something new today. Is the above commands the same in vista to reset the stack?

[JohnWill]

Under certain scenarios, the old WINSOCK fix scrambles some of the registry entries for SP2 and SP3, they changed the registry stack values for those versions with the new TCP/IP stack.

Vista and Windows 7 has a different set for a stack reset, they've been posted here many times...


TCP/IP stack repair options for use with Vista or Windows 7.

Start, All Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.

In the command prompt window that opens, type type the following commands:

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log

Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log

Reboot the machine.