Network Buffer Problem: Internet Failure

[crypted]

Ok, every few days my internet decides to quit working on my computer. Here's the errors that I get:
*An operation on a socket could not be performed because the system lacked sufficient buffers pace or because the queue was full when trying to ssh to 192.168.1.1 (router) from my lan windows xp pc
*xchat on the windows xp pc: Connection failed. Error: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
*websites wont load and ftp connections wont work (ftp error is buffer space problem)
*all active connections remained running but are slowly going down
*cant ping or traceroute any ips except lan computers excluding the router


What I have done to get the internet to work:
1. i rebooted the router first, nothing fixed for the local machine
2. i disabled and reenabled the nic card in network connections on xp and still no go
3. i rebooted the xp machine and its fixed.


I'd like to get this to quit happening as it can be a pain to reboot everything. This used to never happen, but after reinstalling Windows and also installing Fedora to replace the old Redhat7 on the router, it began.

 

[office politics]

from http://68.195.84.12:3333/infowebpages/10055 WinSocks.htm

Solution:
There are following articles in Microsoft Knowledge base:

Windows NT/2000: http://support.microsoft.com/support/kb/articles/Q196/2/71.ASP
Windows 95: http://support.microsoft.com/support/kb/articles/Q170/7/91.ASP

Some users reported to us there is another solution for Windows 95/98/Me which solved the problem at all. Windows 95/98/Me allows up to 100 (default value) of concurrent TCP connections. It looks like when the number of connection reaches the limit 10055 error is reported. The solution is to increase the limit of simultaneous connections. You can do it by changing/creating value of the key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections

If you will create the MaxConnections variable key use STRING type for it (early Windows 95 used DWORD probably). Set the value to 300 for example, restart the Windows and check whether 10055 problem disappeared.

There is MS Knowledge Base article which describes the meaning of MSTCP registry entries:
http://support.microsoft.com/support/kb/articles/Q158/4/74.ASP

 

[crypted]

How am I supposed to add that parameter it speaks of with Windows XP Pro? The Regedit adding is completely different than the one Microsofts Knowledge Base says. I go to Edit, I have to click Add, then DWORD, and then I don't have enough space to add everything they say. I can add a name and then a number value as hexidecimal or decimal. But not all the other junk they say. Could you please translate that incase I'm just being foolish?

 

[office politics]

change the value to 65534 decimal. what you are doing is telling your pc that this is the highest port number it should try to use.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Value Name: MaxUserPort
Data Type: REG_DWORD
Value: 65534
Valid Range: 5000-65534 (decimal)
Default: 0x1388 (5000 decimal)

 

[crypted]

Allright so just by adding the DWORD variable and the data: 65534 it's all set? Because my Regedit is different than the one Microsoft obviously speaks of. I can add the Variable Name and then Variable Data and select a base from Hexidecimal and Decimal, but I have no area to add that Valid Range. The Valid Range portion is what's confusing me.

Right now I've added:
MaxUserPort REG_DWORD 0x0000fffe (65534)
And that's all.

Correct? Or did I mess up? I don't want to reboot and have a dead machine!

 

[office politics]

valid range is just telling you which numbers you can enter into the entry.

you added it correctly

 

[crypted]

Ok, Just for the sake of things I Just found this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;826757
That could very well fix it as it's describing exactly my problem as well, but being Microsoft, I have to pay to get a Hotfix for their screw up. I'm wondering if adding this variable will fix it, or if this Hotfix is a must?