\\computername\c is not accessible Not enough memory

[Eric Lewis]

"Not enough server storage is available to process this
command" is the message I get when I try to access the
contents of a drive on my WinXPpro (1) machine from my
Win2Kserver/Win98 (2) dual-boot machine (running
Win2Kserver). I can access contents of (2) from (1) no
problem. Windows Explorer on (2) can see (1) and the
drive letters of all its shared drives. But I cannot
open the drive tree. I have the same problem with
Win98 "\\computername\c is not accessible Not enough
memory is available. Quit some programs."

The (2) has 512 MB of real memory. (1) has 1 GB of real
memory. So memory is not the issue it would seem. The
system Monitor under Win98 shows about 350 MB of
unallocated real memory.

The problem occurs whether trying to read a 30GB hd, 80GB
hd, CDRW, DVDrom drives. I am able to read and write
onto (2) from (1) so I get around this problem by copying
from (1) to (2).

Does anyone know how to fix this problem?

Thanks in advance, Eric

 

[Ron Lowe]

"Not enough server storage is available to process this
command" is the message I get when I try to access the
contents of a drive on my WinXPpro (1) machine

<snip>

This error indicates that you are falling foul of the IRPStackSize bug.

The problem is on the machine you are attempting to connect to,
not the machine where you see the error message.

On the computer you are attempting to connect to,
Check the event viewer for an event ID 2011.

Usual fix :
You need to fix a parameter called IRPStackSize

On the computer you are attempting to connect to,
Set the IRPStackSize back to the default (15 ).
Perform the following steps:

1. Start the registry editor (e.g., regedit.exe).
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\lanmanserver\parameters.
3. Double-click IRPStackSize
(or if this registry setting doesn't exist,create it of
type DWORD and ensure the case is correct).
4. Change the base to decimal, set the value to 15, and click OK.
5. Reboot the computer.

Norton AV is usual suspect for breaking it.

There's a KB article about this, too.

Antivirus Software May Cause Event ID 2011 (Q177078)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078

 

[Eric Lewis]

Right you are, I corrected the Registry entry, rebooted
all around and now things work as they should. Thanks
for the tip. Eric