S
Sonic98
A friendly recently brought a computer to me after taking
it be repaired and being told he needs a new Nic Card.
After getting me to install the new card for him, I found
that he was still unable to connect to the net. After
both moving the card around to different PCI slots and
removing it to test the built-in ethernet card, I found
that the same problem occured each time.
I was getting this error when trying to renew an IP.
An Operation Was Attempted on Something That Is Not a
Socket.
I figured it was something to do with winsock files or
other files dealing with the network, so I removed all
cards from device manager and remove all connections from
network places. I also ran SFC. No one these helped.
When checking for info in the knowledgebase about the
winsock files I ran across KB article-817571
I removed the winsock registry entries and re-set the
TCP/IP.
I though this would be the solution, but the same error
is still occuring. What else can it be? Could something
be wrong with the actual winsock files themselves? Could
something be wrong with the other registry entries that
the tcp/ip resetting command deals with?
it be repaired and being told he needs a new Nic Card.
After getting me to install the new card for him, I found
that he was still unable to connect to the net. After
both moving the card around to different PCI slots and
removing it to test the built-in ethernet card, I found
that the same problem occured each time.
I was getting this error when trying to renew an IP.
An Operation Was Attempted on Something That Is Not a
Socket.
I figured it was something to do with winsock files or
other files dealing with the network, so I removed all
cards from device manager and remove all connections from
network places. I also ran SFC. No one these helped.
When checking for info in the knowledgebase about the
winsock files I ran across KB article-817571
I removed the winsock registry entries and re-set the
TCP/IP.
I though this would be the solution, but the same error
is still occuring. What else can it be? Could something
be wrong with the actual winsock files themselves? Could
something be wrong with the other registry entries that
the tcp/ip resetting command deals with?