Network drives not accessible

[G''Jim c):{-]

Just recently, my network mapped drives are no longer accessible for storing
data. I keep getting the error message telling me that 'Not enough server
storage is available to process this command'. I get this whether I am
trying to store date to an existing network mapped drive, or whether I
attempt to create a new network mapped drive.

I have searched the archives, of this list, and have already tried the
'IRPStackSize' fix - that didn't correct the problem.

I have also tried turning off the firewall (TrendMicro) on both machines -
Windows Firewall is disabled on all machines on my network.

This is a very recent issue; two weeks ago all my networked mapped drives
worked just fine. Can only conclude that something in a recent update has
created this problem.

I still have access to the NAS on my network, a Galaxy MGB-Quadro-Pro, but
cannot access/create networked mapped drives on other WinXP-Pro machines.

AtDhVaAnNkCsE

[Pegasus [MVP]]

"G''Jim c):{-" > wrote in message
...
> Just recently, my network mapped drives are no longer accessible for
> storing
> data. I keep getting the error message telling me that 'Not enough server
> storage is available to process this command'. I get this whether I am
> trying to store date to an existing network mapped drive, or whether I
> attempt to create a new network mapped drive.
>
> I have searched the archives, of this list, and have already tried the
> 'IRPStackSize' fix - that didn't correct the problem.
>
> I have also tried turning off the firewall (TrendMicro) on both machines -
> Windows Firewall is disabled on all machines on my network.
>
> This is a very recent issue; two weeks ago all my networked mapped drives
> worked just fine. Can only conclude that something in a recent update has
> created this problem.
>
> I still have access to the NAS on my network, a Galaxy MGB-Quadro-Pro, but
> cannot access/create networked mapped drives on other WinXP-Pro machines.
>
> AtDhVaAnNkCsE

Here are a few possible causes and cures:
- Often resolved by applying the latest service pack
- Sometimes caused by NAV or IBM AV:
http://support.microsoft.com/?scid=kb;en-us;177078
- Set
HKLM\SYSTEM\CurrentControlSet\Services\lanmanserve r\parameter\IRPStackSize
to 15..21 decimal
- Sometimes requires server service configuration and tuning
http://support.microsoft.com/default.aspx?scid=kb;[LN];128167
- PoolUsageMaximum set too low:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;304101

Since this is a recent issue, you should use System Restore as a first step.

[G''Jim c):{-]

"Pegasus [MVP]" wrote:


> Here are a few possible causes and cures:
> - Often resolved by applying the latest service pack
> - Sometimes caused by NAV or IBM AV:
> http://support.microsoft.com/?scid=kb;en-us;177078
> - Set
> HKLM\SYSTEM\CurrentControlSet\Services\lanmanserve r\parameter\IRPStackSize
> to 15..21 decimal
> - Sometimes requires server service configuration and tuning
> http://support.microsoft.com/default.aspx?scid=kb;[LN];128167
> - PoolUsageMaximum set too low:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;304101
>
> Since this is a recent issue, you should use System Restore as a first step.
>

I upped the IRPStackSize, again, changed it to 32 (20 hex); at the same time
I noticed that there wasn't any value, at all, for EnableSharedNetDrives.
Added that parameter to the registry, set the value to '1'. Rebooted
computer, and now have shared network drives available once again.

Don't know what caused this problem, to begin with, nor which parameter (or
both) fixed the issue.

G'Jim

[Pegasus [MVP]]

"G''Jim c):{-" > wrote in message
...
>
>
> "Pegasus [MVP]" wrote:
>
>
>> Here are a few possible causes and cures:
>> - Often resolved by applying the latest service pack
>> - Sometimes caused by NAV or IBM AV:
>> http://support.microsoft.com/?scid=kb;en-us;177078
>> - Set
>> HKLM\SYSTEM\CurrentControlSet\Services\lanmanserve r\parameter\IRPStackSize
>> to 15..21 decimal
>> - Sometimes requires server service configuration and tuning
>> http://support.microsoft.com/default.aspx?scid=kb;[LN];128167
>> - PoolUsageMaximum set too low:
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;304101
>>
>> Since this is a recent issue, you should use System Restore as a first
>> step.
>>
>
> I upped the IRPStackSize, again, changed it to 32 (20 hex); at the same
> time
> I noticed that there wasn't any value, at all, for EnableSharedNetDrives.
> Added that parameter to the registry, set the value to '1'. Rebooted
> computer, and now have shared network drives available once again.
>
> Don't know what caused this problem, to begin with, nor which parameter
> (or
> both) fixed the issue.
>
> G'Jim

Thanks for the feedback.