XP Not enough server storage is available to process this command

  • Thread starter Thread starter T. Duprex
  • Start date Start date
T

T. Duprex

Yesterday everything worked fine on my network. I have 2 XPs, and one 98se
via a router to which all are wired.

Today the problem appeared:

My problem is that on one of my XP machines, when I attempt to reach a
share from the other XP machine I get a \\XP_BAD\SharedDocs is not
accessible message with "Not enough server storage is avilable to process
this command"..

The Windows 98se machine can access the shares, no problem just the other
XP

When I open My Network Places on the good XP machine, it shows the other XP
computer connected to the network and the shares on the network, however
when I try to open the share I get the message.

I Googled and went to MSKnowledge base. The only thing the kept showing up
was to increase the number value in IRPStackSize located in HKLM\system
\CurrentControlSet\Services\LanmanServer\Parameters. This problem was
apparently related to a Norton issue.

To begin with, neither of my XP machines had that IRPStackSize entry. As
suggested though I created the word with a decimal value of 15, rebooted,
no change. So I removed it.

I can access the "good" XP shares and the 98 shares from the bad XP. I can
also print from the bad XP over a wireless router connection to a printer.
I just cannot access the share on the bad guy from the good XP machine.

What/where might my problem be. I'd appreciate input and suggestions.


TIA
 
Problem "fixed" but I have no idea why beyond increasing the size of
IPRstackSize made it work. Or why it needed to be increased when
everything worked fine yesterday.


I just went back in and created IRPStackSize but this time I assigned a
digital value of 45, (I read in a second article it has a maximum value of
50 so I figured what the hell) then rebooted. Problem gone.

Question: If I never had a IRPStackSize word to begin with, how did it work
in the first place? Is the 15 value a built in default value, and needs to
be increased based on something that would exceed that value in the
machine?

Now that I have it at 45 is it okay or should I reduce it until it doesn't
work again?

Is the word IRPstackSize case sensitive. I just noticed that the first time
I created it I used IRPStackSize, as the article instructed. The second
time I used IRPstackSize which a different article had detailed.

What would demand the increase in stack size? The only thing that I did
that now comes to mind that might mean something was to update my Acronis
True Image application in both machines. And since that had noting to do
with networking, I didn't associate it with the problem.

TIA
 
Back
Top