Usenet Explorer

I Finally found a way to kill the 10055 error! Yippie!! (kind of).
If I take my NETGEAR router out of the circut and plug directly into the cable modem, the problem goes away. Thats the good news. Called NETGEAR to report the problem, their researching it (I had it all documented). One of the things I apparently forgot to mention was the installation of a new router in my 1st posting.

Meanwhile, until NETGEAR gets off their tush, I'm researching an article:
http://www.proxyplus.cz/faq/articles/EN/art10002.htm

Made modification to my TCP/IP stack maxconnections, in case the Router was keeping more open than my stack will allow. I'll post the results after some more testing.

I receive the error sometimes, but not often, yet I have no router in the loop. I used to have a Linksys 4-port hooked up but it broke, so I just have the DSL modem in there. Soon I will have the Linksys hooked up again though (just bought another one).

I'm not quite sure why my previous post came in as "Guest" after I had logged in, I hope this one does not do the same.

I monitored my connections with the NETGEAR route in place and noticed a multitude of TCP ports with local & foreign addresses 0.0.0.0 in "listening" mode that were persistant and refused to disappear.

Utilizing "netstat -an | more", I saw them build until they were over 100 and @ times 200+. How strange.

Even with my NETGEAR router inline, this article seemed to
diminish if not totally clear out the problem repeated 10055 errors.

http://www.proxyplus.cz/faq/articles/EN/art10002.htm

Basically a reg change to
HKEY_LOCAL_MACHINES\System\Current\ControlSet\Services\VxD\
MSTCP\MaxConections

Changing the default "99" to "300".

Allowes more socket availability over TCP/IP for those that that do not close in a timely fashion. ie.. The ones my router was holding open.