Of Linksys wireless cards and WinSock errors...

Hi, yes, I'm new, but I'll spare you the introductions and get down to business.

I was helping a friend install a WPC54G Linksys wireless card into his laptop (which is running Windows ME), and after we got all of the drivers installed and updated and then tried to set it up on the network, we started getting a WinSock error stating "Socket operation on non-socket". After extensive searching of both Windows and Linksys knowledge bases and support forums as well as just about any concievable related Google search, we still are at a loss.

We've tried uninstalling the card and the drivers together and each separately and the reinstalling. All this has achieved is triggering the same error only when we run the configuration utility. The card does not seem to be communicating with the access point, though it appears that the card is functioning properly. While I was still fiddling with the thing this afternoon the laptop could still establish a wired network connection, though my friend now informs me that he can't even do that anymore.

I cannot imagine why the installation and consequent attempt to use a PCMCIA wireless card would trigger a WinSock related error (though I guess this is after all ME we're talking about...). Then again, these could just as easily be two unrelated problems, one of which just happens to aggrivate the symptom of the other. I really haven't a clue, and to get that admission out of me takes a lot of frustration.

So anyway, I'll answer whatever questions I can that someone might need to help us work on this, but keep in mind that it's not my computer and I don't know the next time I'm going to be able to pump my friend for info as he tends to become incommunicado for long periods of time. I hope someone can help 'cos this is gonna bug me 'til it works.

Thanks in advance,
LaMenta

 

Link to: Repairs Winsock 2 settings.

 

Ahem

http://majorgeeks.com/download.php?det=625

Same app, but local.

 

He tried it and tells me that it still doesn't work. I've directed him to this thread to add his $.02 and whatever other details I may have omitted. This is really starting to bug me. I don't like problems that I can't fix.

 

This page has somthing about reseting TCP/IP may be it can help.

Link to: Sharing Disk Drives Between Computers on Windows Network.

 

I think this post is going to have to serve the purpose of just collecting possible solutions for the next little bit as my friend is going out of the country for 10 days and convincing him to leave his laptop with me to work on is just not gonna happen. So yeah...thanks to everyone who's tried to help so far (none of it has worked yet), I'm still digging for answers myself, and hopefully one will turn up that doesn't involve the reinstallation of the OS, lol.

 

sounds like either tcp isn't bound to the adapter (why ME likes to create that situation I dunno) or McAfee Firewall is off smoking crack again.