The following refers to XoloX, but I have the same problem wih Gnucleus. I post the folliwng on the XoloX forum and someone suggested I try another Gnutella app to see if it casues the same problem. Anyway, I ran Gnucleus for a few hours and the same thing happened, so it may be a problem with all Gnutella clients?

XoloX casues a serious dial up networking probems on my PC running Windows 98 SE, and using a modem. More often than not if I leave XoloX running for a number of hours, my internet connection "dies".

Let me explain:

Sometimes, my PC will remain connected to the net, but my internet connection will by unusable - I can't send or receive any data, not only with XoloX, but with any internet software. If I disconnect from the net, I am able to reconnect and log on as normal, but I still have the same problem. The same applies if I try this a few more times.

Sometimes I have the same problem as above with the only difference being that I actually get disconnected when it occurs.

The only way in which I can restore my intenet access when this problem occurs, is to shut down my computer, and then power up and restart Windows.

NOTE: This is NOT a problem with my ISP but something casued by XoloX, it only ever happens when runnig XoloX.



I have expreienced this problem before on rare occasions before using XoloX/Gnucleus, it was caused by a download manager, maybe FlashGet/JetCar.?




Any help would be greatly appreciated.

Despite what you say I think it probably *is* your ISP or something related to your Internet connection itself. File sharing apps, especially the peer to peer kind, make more intensive use of the network than most other things (web browsing, email and such). To a lesser extent so do download utilities. What all of these have in common is they can create many simultaneous network connections (which it seems may be causing your ISP to crap out).

If it is an ISP problem, why does a complete shutdown and restart always fix the problem. It seems more like a winsock or dial up networking bug.

as far as a i can tell, gnucleus is reaming my DSL.. i have 1.5 mbit professional DSL service, and my entire upstream gets used, despite the fact i set gnucleus to only use 5 k/s.. also, i am NOT uploading any files when this happens..

Unregistered... I'm pretty sure you are having the same problem as we were at work... Windows 98 has a problem of "leaking" network sockets... It's on their support database somewhere (I did research on this a long time ago - last year)... What happens is often times Windows 98 and not the programs will not close out the network sockets after using them... now your supposed to come with 65535 sockets but that's another thing that windows 98 never implemented was full use of the sockets (the number is much lower but I am not sure how much lower)... Essentially though everytime you connect to the net in some fashion you are "eating" up one of these sockets (ie: checking mail, viewing a web page, gnutella connection)... and since windows doesn't close them after use it means that you can't use that socket again during that windows session... a lot of times you can extend the amount of time you get on the net by doing some things... 1) remove ad software as those of times connect back somewhere everytime you load a page 2) lower the frequency that you check your e-mail 3) other things that will prevent unnessecary socket usage...

I spent weeks researching this last year as we were baffled at work... and it was frustrating us to no end... the only way to truely "fix" this problem is to change OS's... we upgraded to Windows 2000 after I found this out and the problem went away immediately... hope this answers your question but unfortunately there is no quick fix...

See also this thread in the Xolox forum:
http://gnutellaforums.com/showthread...&threadid=3863

Thanks milhouse_ph and Moak for the help. I will have to upgrade to Windows 2000 soon it seems... A patch for 98 would be nice, but I guess there isn't one :-(

Has to be more to it than just Win98. I'm running 98 and haven't had this problem - so are many others I know.

well more has progressed since this happened to us...

I pulled this off of Computing.net:

FINALLY!! This did it for me:
Your problem sounds like it's being caused by a corrupted registry entry. In Windows 98, you can try this... Make a backup copy of your registry. Then navigate to H_key_Local_Machine, System, Services. Delete the Winsock2 folder. Then uninstall dial-up networking and re-install it. The re-install will recreate the Winsock2 entries in the registry, and you should be back in business. Very important----> ALWAYS make a backup of your registry before fooling with it, so if something doesn't work as planned you can recover. Let me know if this works.

Looks like it's not nessecarily the OS... I still remember reading something about leaked network sockets on Microsofts Knowledge Base... strange... ;-)

Hope this might work for you...

Thanks milhouse_ph I am about to try it. I wlll post back the findings.