Error "Windows Socket Initialization failed" upon reboot XP Home Edition

  • Thread starter Thread starter Jim
  • Start date Start date
J

Jim

The subject says it all. I did a search in the news group
archives and could not find an exact match.

Been getting this message last week or so. "Windows Socket
Initialization Failed" when rebooting XP.

No networking connectivity would work. My cable modem etc.
is working fine from another computer.

I found refs to a fixing utility but could not down load it.

Any tips would be greatly appreciated !

Thanks
 
Looks like my system is not able to find the netsh ? I get
the error saying some thing about Initialzition helper
initstart in IPMONTR.DLL failed to start with init code of
10107.

Although when I do search for netsh, I see few of them,
including in C:\I386, C:\Windows\I386 etc..giving exact
path to one of these netsh does not work with an error
saying it can not find the file..

I must be missing some thing very basic..
 
Jim,

I've had this same problem in Windows XP Professional for about a wee
also, and I just fixed it!!

When I went in to the Command Prompt and tried to do an ipconfig /rene
, I got the message, "An operation was attempted on something that i
not a socket."

I searched on this message in the Microsoft Knowledge Base and foun
article KB817571. Method #1 fixed my problem. It's basically exportin
the Winsock and Winsock2 registry subkeys under HP_LOCAL_MACHINE t
diskette (because they're corrupted), and deleting them from th
system. Then after rebooting, re-install TCP/IP on top of itself an
re-boot again. My PC came up and I was able to connect to the Interne
once again!

Hope this works for you...Good Luck!! *EE*
*The subject says it all. I did a search in the news group
archives and could not find an exact match.

Been getting this message last week or so. "Windows Socket
Initialization Failed" when rebooting XP.

No networking connectivity would work. My cable modem etc.
is working fine from another computer.

I found refs to a fixing utility but could not down load it.

Any tips would be greatly appreciated !

Thanks * :
Click to expand...


-
efever
 
Jim,

I've had this same problem in Windows XP Professional for about a wee
also, and I just fixed it!!

When I went in to the Command Prompt and tried to do an ipconfig /rene
, I got the message, "An operation was attempted on something that i
not a socket."

I searched on this message in the Microsoft Knowledge Base and foun
article KB817571. Method #1 fixed my problem. It's basically exportin
the Winsock and Winsock2 registry subkeys under HP_LOCAL_MACHINE t
diskette (because they're corrupted), and deleting them from th
system. Then after rebooting, re-install TCP/IP on top of itself an
re-boot again. My PC came up and I was able to connect to the Interne
once again!

Hope this works for you...Good Luck!! *EE*
*The subject says it all. I did a search in the news group
archives and could not find an exact match.

Been getting this message last week or so. "Windows Socket
Initialization Failed" when rebooting XP.

No networking connectivity would work. My cable modem etc.
is working fine from another computer.

I found refs to a fixing utility but could not down load it.

Any tips would be greatly appreciated !

Thanks * :
Click to expand...


-
efever
 
efevers said:
Jim,

I've had this same problem in Windows XP Professional for about a week
also, and I just fixed it!!

When I went in to the Command Prompt and tried to do an ipconfig /renew
, I got the message, "An operation was attempted on something that is
not a socket."

I searched on this message in the Microsoft Knowledge Base and found
article KB817571. Method #1 fixed my problem. It's basically exporting
the Winsock and Winsock2 registry subkeys under HP_LOCAL_MACHINE to
diskette (because they're corrupted), and deleting them from the
system. Then after rebooting, re-install TCP/IP on top of itself and
re-boot again. My PC came up and I was able to connect to the Internet
once again!

Hope this works for you...Good Luck!! *EE*
Click to expand...

=======================================
If you are running Windows XP, then the following article
is the best for dealing with the issue you described:

How to determine and recover from Winsock2 corruption
http://support.microsoft.com/?kbid=811259
=======================================
 
Back
Top