Windoze 9x sockets are pretty weak -- opening too many too quickly causes problems..


I'd turn down my Gnutella client's settings to 2 or 3 connections (I've found specificly that many Gnutella nodes *reject* connection attempts so alot of sockets get opened while searching through the host cache - this is when I sometimes get out of memory errors)

Doing a NETSTAT -AN (in a DOS box) right then I see tons of opened sockets waiting to close...

They do clear in 3.min however you still want to avoid opening them whenever possible - other apps cause problems as well (original Gnutella, GetRight come to mind) when they open too many too fast.

I connect to only 1 or 2 other hosts and note the number of "friends" they have - searches work great.. If you don't find what you want wait a few min then disconnect from those 1 or 2 hosts and connect to another pair, try again (sorta like hopping servers on Napster)

Allow only 1 or 2 D/L's & U/L's, 1 or 2 connections

(Low bandwidth, low socket usage operation for dial-up)

Changing my registry settings and reinstalling DUN didn't work. It seemed to be working, but when I work up this morning my internet connection was dead again. I will now try using fewer connections as the last poster suggested...

You're correct it.
It started happening on my PC with version 1.4.X of Gnucleus.
VERY tiresome to say the least.

Usually this happens when I get a blue screen error message from Win98SE where the message says I perhaps can continue using my PC as usual after the error message. BUT I can't use it since my PC loses connection with internet even though I am still connected to my ISP. Restart seems to be the only salvation.

At last! I was running XoloX for close to 12 hours today with no problems, after reducing the upload speed to 3 KB/second (the upload speed controls the number of connections in XoloX). So basically yes, reducing the number of connections would seem to fix the problem. Of course I was not using Gnucleus, but really the same should apply for any Gnutella client.

Anyway after I have had XoloX running a few more times, I will know for sure whether this is the answer to my problem. I will post the results here.

I've been having the same 'Internet killed' prob's. Funny thing is, when I had Xolox installed on a year-old install of Win98se, Xolox ran with no problems. I just did a wipe and re-installed Win98se, and guess what? Xolox killed my internet (cable modem connection). Nothing short of a reboot would return net access. I had a wild thought and applied system optimizations (for win98 and for cable modems) and the problem is now gone. Get the sysopt.zip file here http://members.home.net/dkh46/sysopt.zip
Maybe it'll work for you, too.

If you are using ZoneAlarm firewall, the program conflict is the cause. You can either shut down the firewall while you are downloading or switch to a different firewall. Sygate personal firewall works allright and you can download it from CNET (download.com). NOTE: if you are using ZoneAlarm and want to uninstall it, visit its website for detailed uninstallation instructions. Don't just use add/remove program. Otherwise, you could crash your computer.

Certainly ZoneAlarm could do this, but it is not the sole cause. I was still having problems after uninstalling ZoneAlarm. After I updated to the latest version of ZoneAlarm it didn't work anymore (unable to start True Vector), so I just ininstalled it.

For the moment I think the only 100% sure fix it to upgrate to 2000 or XP.

Possible solution for a 'dying' or 'freezing' Internet connection using DSL/Cable modem under Windows 98.

After I had this problem with a number of Gnutella clients, it took a couple of days to find a solution that worked for me.

Look in Windows/System for the file NETPPTP.SYS and check the version. If it is older or the same than 4.10.1998 you might want to replace it with a 4.90.3000 version (which can be obtained from the Windows ME edition).

Full report on this issue:
http://support.microsoft.com/support...n_SRCH&SPR=W98

Kind regards,
Mart