• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help! Sudden network failure: Cannot open new sockets. Possible winsock error?

A

Arschloch

Golden Member
Hello all. 🙂

Here are my pertinent system specs:
Win98SE
Duron 700 MHz
192 Megs RAM
3com 10mbit network card

I am at a university that uses Ethernet for its internet connection method for us students.

This problem seemingly came out of nowhere. I rebooted my computer this evening, and when I got into Windows, my Email notifying program gave me some kind of "socket error" and crashed. Then I tried opening up INternet Explorer, which crashed immediately. Then I tried opening telnet, which crashed as soon as I tried to connect to anything.

When I opened Audiogalaxy Satellite, it says something to the effect that it "Cannot open any more sockets! Run the WInsock 2 update if you are running windows 95." Of course, I'm in 98SE, so this should not be an issue.

My newsreader, XNews, says that it is unable to open a new socket. Serv-U FTP says that it is unable to open a listening socket.

That is pretty much the rundown of my internet utilities. I figured that this might be a winsock error. I did a search for "wsock32.dll" on my hard drive, and it only found one, a 40kb file, in the windows/system directory, which I believe is correct.

I did not delete or run any programs right before that last reboot -- as I said, it was completely sudden.

Given that it's giving me all of these socket errors or the applications are just crashing immediately, what do you think the problem is? Any suggestions? Has anyone seen anything similar? I'm desperate for help here.

Thanks.
-Arschloch 🙂
 
Oh, and I forgot to add: the 'ping' command at the DOS Prompt works just fine. I understand that the ping command uses the 16-bit winsock command, which is another reason why I figured that there might be a problem with wsock32.dll.

-Arschloch 🙂
 
*bump*

Sorry to *bump* so soon after posting it, but I -have- to have this problem fixed by the end of today (Thursday). Today is the last day I have easy access to someone else's computer for internet purposes, because I move out tomorrow.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top