Is "not enough memory" error due to XP security patches?

  • Thread starter Thread starter Martin
  • Start date Start date
M

Martin

Recently, my home networked Win95 and WinMe computers
stopped being able to access the shared resources on my XP
computer.

All three computers are able to access the internet
through the SMC Barricade router. The XP computer can
access the shared drives on the other two computers.
However, when the Win 95 & Me computers attempt to access
one of the XP drives, the following error occurs:
"\\XPcomputer\xp_d is not accessible."
"Not enough memory is available. Quit some programs."
(when trying to access the "D:" drive on the XP computer)

Similarly, when trying to print to the printer attached to
the XP computer the following error message is shown:
"There was an error writing to \\XP computer for printer(..
"There is not enough memory available to print your
document. Quit one or more programs and try again. ..."

I did try unloading memory resident programs and modules,
but this did not help, and I can't think of any recent
changes on these machines. All machines have been scanned
for viruses with up-to-date virus data (Symantec). The
only recent change has been installing a number of
security patches on the Win XP computer (and a couple on
the Win Me computer) during the msblast worm scare.

Has anyone else had this problem and do you have a
solution?

Thanks in advance for any assistance!
Martin
 
"Martin" said:
Recently, my home networked Win95 and WinMe computers
stopped being able to access the shared resources on my XP
computer.

All three computers are able to access the internet
through the SMC Barricade router. The XP computer can
access the shared drives on the other two computers.
However, when the Win 95 & Me computers attempt to access
one of the XP drives, the following error occurs:
"\\XPcomputer\xp_d is not accessible."
"Not enough memory is available. Quit some programs."
(when trying to access the "D:" drive on the XP computer)

Similarly, when trying to print to the printer attached to
the XP computer the following error message is shown:
"There was an error writing to \\XP computer for printer(..
"There is not enough memory available to print your
document. Quit one or more programs and try again. ..."

I did try unloading memory resident programs and modules,
but this did not help, and I can't think of any recent
changes on these machines. All machines have been scanned
for viruses with up-to-date virus data (Symantec). The
only recent change has been installing a number of
security patches on the Win XP computer (and a couple on
the Win Me computer) during the msblast worm scare.

Has anyone else had this problem and do you have a
solution?

Thanks in advance for any assistance!
Martin
Click to expand...

That error message is very misleading. The problem is probably that a
the antivirus program has changed an obscure TCP/IP setting. Please
see this Microsoft Knowledge Base article for a likely solution,
specifying a value of 15 for IRPStackSize on the XP computer:

Antivirus Software May Cause Event ID 2011
http://support.microsoft.com/?scid=kb;en-us;177078
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
:mad:

I also had this problem several times for unknown reasons. There is a trick to be sure which PC is faulty : try to mount a local shared folder as a remote disk. For instance if my PC is named "MyPC" and I have shared a folder like C:\My Documents\Tmp as \\MyPC\Tmp, from MyPC, I chose "connect network drive" from the XP file explorer, select "Browse", Network/Group and select \\MyPC\Tmp. Then, when the PC is faulty, I get an error message saying "not enough Memory on the server".

This happened to me first when I installed a Paragon-GmBH software, Drive Backup. As soon as I removed it, the share feature was OK again.

Recently it happened to me again on another PC, but this time I chose to restore the system from a backup.

Now this has happened again, for no obvious reason, but I suspect it has been there for quite some time, and I would prefer to avoid to revert to a very old system version, just to solve this (everything else is doing fine).

.Merle1.
 
:mad:

I also had this problem several times for unknown reasons. There is a
trick to be sure which PC is faulty : try to mount a local shared folder
as a remote disk. For instance if my PC is named "MyPC" and I have
shared a folder like C:\My Documents\Tmp as \\MyPC\Tmp, from MyPC, I
chose "connect network drive" from the XP file explorer, select
"Browse", Network/Group and select \\MyPC\Tmp. Then, when the PC is
faulty, I get an error message saying "not enough Memory on the
server".

This happened to me first when I installed a Paragon-GmBH software,
Drive Backup. As soon as I removed it, the share feature was OK
again.

Recently it happened to me again on another PC, but this time I chose
to restore the system from a backup.

Now this has happened again, for no obvious reason, but I suspect it
has been there for quite some time, and I would prefer to avoid to
revert to a very old system version, just to solve this (everything
else is doing fine).

Merle1.
Click to expand...

Not seeing the complete error message, it's hard to be sure. The most common
occurrence of this error, though, is caused by an IRPStackSize setting.
<http://nitecruzr.blogspot.com/2005/06/server-functionality-affected-by.html>
 
Hi Merle One-

I thank you for your kind and suggestive comments, I don't think my problem
is with "Paragon-GmBH software", but I understand that some Norton AntiVirus
program is the cause. Norton has a tenderancy to cause network issues. It's a
great AntiVirus software, but unfortunately it seriously causes too many
issues with networking.

I believe I will try your suggestion below about: "try to mount a local
shared folder
as a remote disk", although I feel like you do that it will still cause me this problem. Sounds like the registery might need the tweaking as suggested. I've tried something similar eariler before placing a posting here on the network... and the same results occurred. I think, like Chuck suggested, that the registery needs to address the "IRPStackSize setting."
Click to expand...

I thank you, and will keep this in mind in case this doesn't work for me.

Again, thanks!
 
Update : :) :)
I followed your hint, that is increase the IRPStackSize, the register entry that lays in the
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
area.

I firstly observed that the key was missing, which is supposed to be OK to let XP manage this parameter on its own (on a clean PC the key is also missingà.

Following the instructions, I created the corresponding DWORD, setting 15 (decimal) as value : after reboot problem was still there. I changed the value to 18 and after reboot : it works !!!!

Thanks to all.

Regards,

.Merle1.
 
Thanks Merle-

I do appreicate it! I will change the value from the suggestive 11 to 18 and
then reboot... hopefully our problem will disappear... let you know if it
doesn't!

D. Morales
 
Update : :) :)
I followed your hint, that is increase the IRPStackSize, the register
entry that lays in the
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
area.

I firstly observed that the key was missing, which is supposed to be OK
to let XP manage this parameter on its own (on a clean PC the key is
also missingà.

Following the instructions, I created the corresponding DWORD, setting
15 (decimal) as value : after reboot problem was still there. I
changed the value to 18 and after reboot : it works !!!!

Thanks to all.

Regards,

Merle1.
Click to expand...

The observation, that even adding a key with an increased value, can be
productive, is useful here. Thank you very much for updating the thread!
 
Hi Chuck-

Yes, I thank you both - all that has advise me on this account, I will
simply apply this tactic to my customer's PC.

Again, thanks!
 
No problem, seems normal to do so. I'd like to add that I also found in the process another strong hint to the solution :
I looked at the system event log and it was explicitely stated there to increase the IPRStackSize value (but without saying how or to which level).

Best regards,

.Merle1.
 
Back
Top