blackoutspy said:
I have a share set up on my windows machine, and i've been usin it a while and all of the sudden, i can't connet. I keep getting a error, -36. I have no idea what is going on, and i hoped someone had this problem and had a little insight.
I was getting this too, and then realized that other PCs on the network couldn't reach my XP machine as well. I have had the problem before and performed these instructions and everything worked again. Don't know why Windows randomly changes registry entries and never installs the same way twice. Give this a try and see if it applies to you:
Not enough server storage is available to process this command
Monday, June 30, 2003 at 2:25 pm
Windows XP Annoyances Discussion Forum
Posted by Ann [find other messages by Ann]
.... not so elementary my dear watson!
REFERENCE:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;106167
and for clear/crisp registry edit instructions:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q177078
This is one of those annoying occasions where feeding the error message into the MS KB search engine does not yield either of the above two KB articles which quote the very same error message!
The KEY WORDS in the error messages that I was seeing were the last line:
from WinXP:
Not enough server storage is available to process this command.
from Win98se:
Not enough memory to complete transaction. Close some applications and retry.
THE FIX:
check registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
for an IRPStackSize value. In my case that value was 11 (decimal) and MS KB advises WinXP users to increase it by 3 however I chose to increase it to the WinXP default value of 15. (other OS users should check the KB article since the default appears to be different) (This was done on both WinXP machines in my network.)
A reboot of both machines following this registry edit and the majority of network shared folders were once again accessible. I needed to delete a few and recreate them but adding these new network places went smoothly after this fix.
KUDOS:
Acknowledgement to Hans-Georg Michna who had responded on the MS WinXP Networking newsgroup with helpful advice to others with related network problems and who had a web page that directed me to the above two MS KB articles:
http://www.michna.com/kb/WxNotEnoughServerStorage.htm
ROOT CAUSE:
I don't know. Norton AV appears to be implicated but I can't access the relevant Symantec web site knowledge base article. My guess is that a stacksize of 11 was optimal up until the point that I introduced the newer hardware to the network. Maybe there are more levels required in the stack due to one of the many new features found on this newly introduced MB (the RTL8201BL PHYceiver chip being the most probable candidate in my mind). Maybe a clean install of XP would have resulted in the default value of 15 being assigned to this parameter. Maybe, maybe ..... !
OTHER REFERENCES:
for the very curious read about IRPstacksize (albeit from an NT perspective) at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;102967
http://support.microsoft.com/default.aspx?scid=kb;en-us;97599
http://support.microsoft.com/default.aspx?scid=kb;en-us;102974
finally Norton AntiVirus seems to be implicated but the Symantec web server is down so I can't access the following referenced URL to learn more:
http://service1.symantec.com/suppor...pendocument&highlight=0,enough,server,storage
Written in response to:
ability to browse shared folders is one-way on a WinXP peer-peer network (Ann: Saturday, June 28, 2003 at 5:21 pm)
