Socket error 10093

[Byte 2.0]

I am doing some research on an error that has been popping up after the release of some new setup software.

sorry I have to remain vague about some details.

the problem occurs mostly on win98/ME computers.

There are many unknowns so far, but as far as I know the main related issue is they all used the same software.

What I am looking for is a fix for the error.

Here are some of the simpthoms,

Connect, no surf.

Ping by IP, but not HOST name

FTP command gives the error with socket 10093.

So far we have known issues with win98 FE/SE and ME.

people that are efected can not surf or email with IE 4.0 5.0 5.5 or 6.0 or use any of the related outlook express programs.

Here is a kicker, Netscape can surf and receive email, CAN NOT SEND EMAIL.

I have not personally got to touble shoot one of the computer with a customer but several have so far.

Reinstalling Com stack and TCP/IP seems to have no effect.

reinstalling the NIC, seems to have no effect,

It can happen with USB modems as well.

We have tried LSP FIX and other programs that are very good at repairing the winsock file system
winsockxp.exe which seems to work on most verisons of windows.

Some of the effected computers, have Norton Internet securities, we are wondering if the software programs are conflicting.

Most of the effected computers, we have not had a chance to run spybot or ad aware on because we could not get them surfing, have mailed them netscape CD's in the meantime.

We have been searching Microsoft we are finding causes but no solutions.

I took a crash PC and installed firewalls, antivirus, installed uninstalled programs screwed up the TCP/IPs run the same install wizard that we supect is the problem and I have yet been unable to reproduce the error. I will be spending more time tomorrow trying to reproduce it.

My concern is that the wizard is causing problems and we need to be able to provide a solution other then reinstalling windows.

tonight i am making a CD with tons of spyware to install on a crash system then going to run the program over again.

I honestly believe if I get my hands on a system with that error I will be able to find the solution, but I am not going to find it talking to a person over the phone.

[glc]

By any chance, do all these systems have AOL software on them? That can do some really nasty things to 98/ME systems, especially 8.0 and 9.0.

Another thing that can cause socket errors like that are port monitor programs - they keep ports open and you can't open a port that's already open.

[Byte 2.0]

no aol software that I am aware of, not to say their isn't any. I will add that to the check list.

I have been unable to reproduce the error myself.

[GaryRouth]

I imagine your programmers have already looked at the error details, but maybe they missed something. I looked around a bit, and there seemed to be a few possible problems: 1) different WinSock versions 2) more than one active 3) a failure of the subsystem to start 4) "too many WSACleanUp calls" 5) incorrect path [...I'm sure your programming team knows these much better than I ever will... but I suppose anyone can miss something sometime]

Several online programming guides had these details:

WSANOTINITIALISED (10093) Successful WSAStartup() not yet performed
Berkeley description: No equivalent.
WinSock description: Either your application hasn't called WSAStartup(), or WSAStartup() failed, or--possibly--you are accessing a socket which the current active task does not own (i.e. you're trying to share a socket between tasks). Note the British spelling (with an 'S' instead of a 'Z').
User suggestions: Chances are the network subsystem is misconfigured or inactive. See WSASYSNOTREADY for details.
Developer suggestions: WSAStartup() failed, and you didn't detect it, or it wasn't called for the current task at all, or you called WSACleanup() too many times.
WinSock functions: accept(), bind(), closesocket(), connect(), gethostbyaddr(), gethostbyname(), gethostname(), getpeername(), getprotobyname(), getprotobynumber(), getservbyname(), getservbyport(), getsockname(), getsockopt(), ioctlsocket(), listen(), recv(), recvfrom(), select(), send(), sendto(), setsockopt(), shutdown(), socket(), WSAAsyncGetHostByAddr(), WSAAsyncGetHostByName(), WSAAsyncGetProtoByName(), WSAAsyncGetProtoByNumber(), WSAAsyncGetServByName(), WSAAsyncGetServByPort(), WSAAsyncSelect(), WSACancelAsyncRequest(), WSACancelBlockingCall, WSACleanup(), WSASetBlockingHook(), WSAUnhookBlockingHook()
Additional functions: The only function capable of failing with a WinSock error that doesn't list error is WSAUnhookBlockingHook(). Clearly, this oversight was not intentional.

WSASYSNOTREADY (10091) Network subsystem is unavailable
Berkeley description: No equivalent.
WinSock description: The WinSock implementation cannot function at this time, because the underlying system it uses to provide network services is currently unavailable.
User suggestions:
„h Check that the WINSOCK.DLL file is in the current path
„h Check that the WINSOCK.DLL file is from the same vendor as your underlying protocol stack. You cannot mix and match (WINSOCK DLLs must be supplied by the same vendor that provided your underlying protocol stack).
„h You cannot use more than one WinSock implementation simultaneously. If you have more than one WINSOCK DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded.
„h Check your WinSock implementation documentation to be sure all necessary components are currently installed and configured correctly.
WinSock functions: WSAStartup()

Sorry if they've looked at this stuff a hundred times already and want me tarred and feathered for mentioning them. . .
. . . Gary

[Byte 2.0]

HA HA, I didn't find it and sorry took me so long to get back to post this but we did bet our advanced solutions department at finding a fix. I can't take the credit for it, I was really just a support person at best, but it was as simple as deleting 3 .Dll files and rebooting.

Sorry I dont' have them with me, I will do my best to remember and post them here tomorrow.

Another guy found the fix and we got to pass it allong to our advanced group.