Socket Error

  • Thread starter Thread starter Home Network Rookie
  • Start date Start date
H

Home Network Rookie

I have been attempting to network my laptop computer to
my home desktop on a wireless basis. When the connection
didn't work I contacted the network card vendor
(Netgear). After trying several different approaches,
the helpdesk lady asked me to run cmd "ipconfig/renew".
The following message appeared:

"An error occured while renewing interface wireless
connection 4: An operation was attempted on something
that is not a socket."

She said that a socket.DLL file was missing and that I
should contact Microsoft to get instructions on how to
restore this file. Has anyone else encountered this
problem and figured out how to fix it? I would
appreciate any assistance.

Home Network Rookie
 
I have encountered the same problem, but in my case it
keeps recurring. Anyone have any ideas on how to find out
why the sockets keep getting corrupted, or why it keeps
recurring? A "third party program" (per Microsoft) doesn't
give me much to go on... (In my case, system restore works
to repair, but I can't be running restore every 2-4 days!)
Any thoughts would be appreciated!

-Scott
 
Run "winmsd" and go to Components/Network/Protocol. Look at the names in
the list, anything with "MSAFD" in it or the "RSVP xxx Service Provider"
should be fine. Anything else is suspect, and uninstalling the owning
program might help.


Here is my catalog for comparison, with my comments in parens

1012 - WinSock Proxy [tcp] (Microsoft Firewall Client - most users won't
have this)
1013 - WinSock Proxy [udp] (Microsoft Firewall Client - most users won't
have this)
1014 - WinSock Proxy for RSVP [tcp] (Microsoft Firewall Client - most users
won't have this)
1015 - WinSock Proxy for RSVP [udp] (Microsoft Firewall Client - most users
won't have this)
1001 - MSAFD Tcpip [TCP/IP] (Required for internet access)
1002 - MSAFD Tcpip [UDP/IP] (Required for internet access)
1003 - MSAFD Tcpip [RAW/IP] (Optional, but normal)
1004 - RSVP UDP Service Provider (Optional, but normal)
1005 - RSVP TCP Service Provider (Optional, but normal)
(The number of the following and the long number in each line will differ
from machine to machine, optional but normal)
1040 - MSAFD NetBIOS
[\Device\NetBT_Tcpip_{0C017D01-0D2F-409D-A367-D3992137A6A4}] SEQPACKET 0
1041 - MSAFD NetBIOS
[\Device\NetBT_Tcpip_{0C017D01-0D2F-409D-A367-D3992137A6A4}] DATAGRAM 0
1042 - MSAFD NetBIOS
[\Device\NetBT_Tcpip_{D887D9DA-ECB6-43B3-AC0B-499F8D5EFC24}] SEQPACKET 1
1043 - MSAFD NetBIOS
[\Device\NetBT_Tcpip_{D887D9DA-ECB6-43B3-AC0B-499F8D5EFC24}] DATAGRAM 1
1044 - MSAFD NetBIOS
[\Device\NetBT_Tcpip_{816F4507-E42B-4551-8D55-8A193826F9E3}] SEQPACKET 2
1045 - MSAFD NetBIOS
[\Device\NetBT_Tcpip_{816F4507-E42B-4551-8D55-8A193826F9E3}] DATAGRAM 2

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


I have encountered the same problem, but in my case it
keeps recurring. Anyone have any ideas on how to find out
why the sockets keep getting corrupted, or why it keeps
recurring? A "third party program" (per Microsoft) doesn't
give me much to go on... (In my case, system restore works
to repair, but I can't be running restore every 2-4 days!)
Any thoughts would be appreciated!

-Scott
 
Thanks for letting us know Scott.

Lance
*****

Scott Hastings thought carefully and wrote on 9/25/2004 1:30 PM:
 
Back
Top