windows sockets initialization failure error in licenset window

Got the above error on an XP Pro stand alone which has been up for almost a
year after clients sons from college showed a music based slide show from a
thumb drive. Then the above error showed up. Now she can't get to the
internet via 10/100 cable modem. Contacted Bresen Cable (ISP) techinical who
tried to reset the cable modem. Checked IP Address (found to be 0,0,0,0 with
auto configuration checked) Went to the Command (DOS) window by running CMD.
Tried ipconfig /release (said already released) tried ipconfig /renew (said
could not access RPC server) Kept getting error on RPC Server when we tried
to renew the IP Address. Probably from the socket init. failure error above.
Checking the winsocket files (winsock.dll and wsock32.dll show their specs
to be idential to my files for size and specs on my Motion 1300). The specs
are
FILE: c:\windows\system32\winsock.dll
SIZE: 2.80 KB (12,864 bytes)
VERSION: 3.10
and
FILE: c:\windows\system32\wsock32.dll
SIZE: 22.00 KB (22,528 bytes)
VERSION: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)

The system is a 935mHz HP Pavillion, 128MB ram, 80 GB hd. Note the low RAM.
I believe that the window socket files are corrupt but how do I fix?? I
thought about just copying my files on to the client computer or backing up
and reinstalling XP totally.
Any ideas?
--
Milt Trosper

How to determine and recover from Winsock2 corruption
http://support.microsoft.com/kb/811259/en-us

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

-------------------------------------------------------------------------------------------

"Milt" wrote:

| Got the above error on an XP Pro stand alone which has been up for almost a
| year after clients sons from college showed a music based slide show from a
| thumb drive. Then the above error showed up. Now she can't get to the
| internet via 10/100 cable modem. Contacted Bresen Cable (ISP) techinical who
| tried to reset the cable modem. Checked IP Address (found to be 0,0,0,0 with
| auto configuration checked) Went to the Command (DOS) window by running CMD.
| Tried ipconfig /release (said already released) tried ipconfig /renew (said
| could not access RPC server) Kept getting error on RPC Server when we tried
| to renew the IP Address. Probably from the socket init. failure error above.
| Checking the winsocket files (winsock.dll and wsock32.dll show their specs
| to be idential to my files for size and specs on my Motion 1300). The specs
| are
| FILE: c:\windows\system32\winsock.dll
| SIZE: 2.80 KB (12,864 bytes)
| VERSION: 3.10
| and
| FILE: c:\windows\system32\wsock32.dll
| SIZE: 22.00 KB (22,528 bytes)
| VERSION: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
|
| The system is a 935mHz HP Pavillion, 128MB ram, 80 GB hd. Note the low RAM.
| I believe that the window socket files are corrupt but how do I fix?? I
| thought about just copying my files on to the client computer or backing up
| and reinstalling XP totally.
| Any ideas?
| --
| Milt Trosper

Removed the Winsock components, reinstalled the TCP/IP and VOLA the internet
connection jumped to life.
Thanks for the info.
from a happy consultant and a happier client
Milt
--
Milt Trosper


"Milt" wrote:

Got the above error on an XP Pro stand alone which has been up for almost a
year after clients sons from college showed a music based slide show from a
thumb drive. Then the above error showed up. Now she can't get to the
internet via 10/100 cable modem. Contacted Bresen Cable (ISP) techinical who
tried to reset the cable modem. Checked IP Address (found to be 0,0,0,0 with
auto configuration checked) Went to the Command (DOS) window by running CMD.
Tried ipconfig /release (said already released) tried ipconfig /renew (said
could not access RPC server) Kept getting error on RPC Server when we tried
to renew the IP Address. Probably from the socket init. failure error above.
Checking the winsocket files (winsock.dll and wsock32.dll show their specs
to be idential to my files for size and specs on my Motion 1300). The specs
are
FILE: c:\windows\system32\winsock.dll
SIZE: 2.80 KB (12,864 bytes)
VERSION: 3.10
and
FILE: c:\windows\system32\wsock32.dll
SIZE: 22.00 KB (22,528 bytes)
VERSION: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)

The system is a 935mHz HP Pavillion, 128MB ram, 80 GB hd. Note the low RAM.
I believe that the window socket files are corrupt but how do I fix?? I
thought about just copying my files on to the client computer or backing up
and reinstalling XP totally.
Any ideas?
--
Milt Trosper