wireless nodes cannot connect to external drive (USB) on base unit

[Guest]

Hello,

Can somebody help me with this problem? I have a base unit running Win2000
Pro, and two laptops running WinXP. In addition to two internal HD I also
have two 160GB Western Digital external drives (USB). From the base I can
see all the drives and move files between them with no problem.

The problem is that on the two wireless units I can't map a drive to the
external units on the base. Apparently they can find the drives (using
browse to search for shared devices), but when I map to it and press "Finish"
I get the following message:

'The mapped networked drive could not be created because the following error
has occured --- not enough server storage is available to process the
command'.

They used to be able to connect, but now they can't. I had installed new
versions of Norton System Works, Anti-virus, Personal Firewall, and
Anti-Spam. But other than that things are pretty much the same as when they
were working. I'm pretty sure the problem must be with the base unit since I
get the same message on both of the laptops.

Can anyone help with this?

Thanks.

 

[Chuck]

On Sat, 25 Jun 2005 09:26:02 -0700, "Dwight Gard" <Dwight

Hello,

Can somebody help me with this problem? I have a base unit running Win2000
Pro, and two laptops running WinXP. In addition to two internal HD I also
have two 160GB Western Digital external drives (USB). From the base I can
see all the drives and move files between them with no problem.

The problem is that on the two wireless units I can't map a drive to the
external units on the base. Apparently they can find the drives (using
browse to search for shared devices), but when I map to it and press "Finish"
I get the following message:

'The mapped networked drive could not be created because the following error
has occured --- not enough server storage is available to process the
command'.

They used to be able to connect, but now they can't. I had installed new
versions of Norton System Works, Anti-virus, Personal Firewall, and
Anti-Spam. But other than that things are pretty much the same as when they
were working. I'm pretty sure the problem must be with the base unit since I
get the same message on both of the laptops.

Can anyone help with this?

Thanks.

Dwight,

This is a well known error, probably caused by NAV.
<http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html>

 

[Thomas Wendell]

With the phrase "not enough server storage is available to process " I
searched google and come up with a lot....
This is one:

Not enough server storage

Not enough server storage is available to process this command.

Not enough memory to complete transaction. Close some applications and
retry.

These error messages can indicate the IRPStackSize bug on the other
machine (the server that has the share). On that computer open the
event log and check for event ID 2011. If this is present, it is a strong
indication for this particular bug.

To repair it, you have to reset the IRPStackSize parameter back to its
default value of 15 on the server where the share is.

HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Services
\lanmanserver
\parameters

Check for the presence of a value named IRPStackSize. If it doesn't
exist, create it as type DWORD. With base set to decimal, enter the
value 15.

Reboot the computer.

One frequent culprit is Norton AntiVirus, which tends to change this
parameter.

Check also this Microsoft Knowledge Base article. It does not mention
Windows XP, but applies to XP as well.

Antivirus Software May Cause Event ID 2011 (Q177078)
http://support.microsoft.com/kb/177078/


--
Tumppi
Reply to group
=================================================
Most learned on nntp://news.mircosoft.com
Helsinki, Finland (remove _NOSPAM)
(translations from FI/SE not always accurate)
=================================================

 

[Guest]

Chuck,

Thanks very much for the tip. And thanks especially for such a quick
response. I think it was no more than 15 minutes before I had a response.
Your solution was dead on and fixed the problem right away. I have to
wonder, though, if this is a continuing problem with NAV, why in the heck
don't they prevent their software from creating this kind of problem in the
first place. I'm guessing that installing NAV somehow modifies that registry
item sense it changed from its default value.

Anyway, thanks for your help. The problem was driving me crazy.

Regards,

Dwight Gard

 

[Guest]

Hello Thomas,

Thanks for the tip. That was exactly what was going on with my problem and
that procedure fixed it.

Thanks for the prompt response.

Regards,

Dwight Gard

 

[Chuck]

Chuck,

Thanks very much for the tip. And thanks especially for such a quick
response. I think it was no more than 15 minutes before I had a response.
Your solution was dead on and fixed the problem right away. I have to
wonder, though, if this is a continuing problem with NAV, why in the heck
don't they prevent their software from creating this kind of problem in the
first place. I'm guessing that installing NAV somehow modifies that registry
item sense it changed from its default value.

Anyway, thanks for your help. The problem was driving me crazy.

Regards,

Dwight Gard

Dwight,

Thanks for the update, and the feedback. I sometimes wonder about Symantec,
too, but I try not to do so for too long. ;-}