Unable to map to any shares on a pc

[itgirl]

I have a Windows XP Pro SP2 machine that all of a sudden won't allow anyone
to connect to any shares. The message we get when we try to map a drive to
any of the shares including admin shares is; The mapped network drive could
not be created because the following error has occurred: Not enough server
storage is available to process this command.
There is plenty of space on all the pc's (including the one in quesstion)
that we are trying to map it on. It doesn't matter that we are
administrators on the domain or local admins.

 

[wilscott1st]

I have a Windows XP Pro SP2 machine that all of a sudden won't allow anyone
to connect to any shares.  The message we get when we try to map a driveto
any of the shares including admin shares is; The mapped network drive could
not be created because the following error has occurred: Not enough server
storage is available to process this command.
There is plenty of space on all the pc's (including the one in quesstion)
that we are trying to map it on.  It doesn't matter that we are
administrators on the domain or local admins.

I did a quick search and found this, apparently usually associated
with Norton AntiVirus.
Definatley not my own knowledge but it made me curious....

From MVP Hans-Georg Michna

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 regedit.
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 with 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

hope it helps!

 

[itgirl]

I actually found that document before posting and tried several different
values to no avail. I just found a post on another site that said they set
the value to 21 and it resolved his problem. I will try that, but keep
posting answers for me.

Thanks!

 

[Pegasus \(MVP\)]

I have a Windows XP Pro SP2 machine that all of a sudden won't allow anyone
to connect to any shares. The message we get when we try to map a drive
to
any of the shares including admin shares is; The mapped network drive
could
not be created because the following error has occurred: Not enough server
storage is available to process this command.
There is plenty of space on all the pc's (including the one in quesstion)
that we are trying to map it on. It doesn't matter that we are
administrators on the domain or local admins.

This is usually resolved by applying the latest service pack.
It can also be caused by NAV or IBM AV:
http://support.microsoft.com/?scid=kb;en-us;177078
Sometimes the server service needs configuration and tuning
http://support.microsoft.com/default.aspx?scid=kb;[LN];128167

 

[itgirl]

Thanks for your responses. I have resolved the issue. I set the
IRPStackSize to a value of 21 and was able to map the shares.

Again thanks for the help.

I have a Windows XP Pro SP2 machine that all of a sudden won't allow anyone
to connect to any shares. The message we get when we try to map a drive
to
any of the shares including admin shares is; The mapped network drive
could
not be created because the following error has occurred: Not enough server
storage is available to process this command.
There is plenty of space on all the pc's (including the one in quesstion)
that we are trying to map it on. It doesn't matter that we are
administrators on the domain or local admins.

This is usually resolved by applying the latest service pack.
It can also be caused by NAV or IBM AV:
http://support.microsoft.com/?scid=kb;en-us;177078
Sometimes the server service needs configuration and tuning
http://support.microsoft.com/default.aspx?scid=kb;[LN];128167