Mapped file share unavailable within seconds

[Grundy]

I can map a file share on an XP Home PC on my LAN. I can then see all the
subfolders and files on the share. But within a minute or less, that share
then becomes unavailable. Now if I try to map the same share, there is a
delay followed by an error "the network path \\system\share could not be
found

After a few hours (and no other action need be taken), the above is
repeatable - Ican map the share again, but only for about a minute before it
becomes unavailable.

I get the same behavior when attempting to map the share from two different
PCs, both running XP Home also. Reboots of both the clients and the server
machines make no difference.

I've never seen such odd behavior and would appreciate help to resolve.

Thanks.

 

[Grundy]

I can map a file share on an XP Home PC on my LAN. I can then see all the
subfolders and files on the share. But within a minute or less, that share
then becomes unavailable. Now if I try to map the same share, there is a
delay followed by an error "the network path \\system\share could not be
found

After a few hours (and no other action need be taken), the above is
repeatable - Ican map the share again, but only for about a minute before it
becomes unavailable.

I get the same behavior when attempting to map the share from two different
PCs, both running XP Home also. Reboots of both the clients and the server
machines make no difference.

I've never seen such odd behavior and would appreciate help to resolve.

Thanks.

More data: I get an error in the System Event Log on the server when the
subsequent attempt to map the share fails: Event ID 2021.

 

[Anteaus]

A possibility:
http://mylogon.net/support/psave

 

[Grundy]

Thanks for the suggestion. This isn't the problem because the affected PC is
still accessible on the network (I can ping it, it can access the internet,
it can even map a share on other PCs).

 

[Chuck [MVP]]

More data: I get an error in the System Event Log on the server when the
subsequent attempt to map the share fails: Event ID 2021.

The "Event ID 2021" message suggests a resource problem on the server (target
computer).
<http://support.microsoft.com/kb/317249>
http://support.microsoft.com/kb/317249

You can Google for "Event ID 2021" if you like, and a few search hits will
contain links to articles which simply link to the Microsoft post. JSI, a long
time expert in Windows Networking issues, does just that.
<http://windowsitpro.com/article/art...do-i-troubleshoot-event-id-2021-and-2022.html>
http://windowsitpro.com/article/art...do-i-troubleshoot-event-id-2021-and-2022.html

How many computers do you have in your LAN? What sort of activity do you have?

I would start by looking at the number of connections that you are creating.
Computers running XP Home are limited in this resource.
<http://networking.nitecruzr.net/2005/07/server-availability-affected-by.html>
http://networking.nitecruzr.net/2005/07/server-availability-affected-by.html

Is this one specific computer, that's giving this problem? If so, what's
different about this computer? Some discussions of the "Event ID 2021" suggest
network driver problems, so make sure that you have the latest drivers for your
network adapters, from the vendor.
<http://nitecruzr.blogspot.com/2005/08/driver-updates-from-microsoft-please.html>
http://nitecruzr.blogspot.com/2005/08/driver-updates-from-microsoft-please.html

 

[Grundy]

Thanks Chuck.

More info: when I first tried to map this share, I got "not enough server
storage is available". So I followed this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078
as I have done on other systems before. With IRPStackSize set to 35 decimal,
I could now map the share. But as described, the mapped drive becomes
inaccessible within about 30 seconds, and cannot be established for some time
after that (hours possibly). Then the cycle repeats: I can map the share,
open a file or view a folder contents, then it becomes inaccessible again.

Note that even when inaccessible to the map command in Explorer, I can still
ping the "server" system, and it is able to map a file share on other XP
systems.

I am running Norton Internet Security 2006 on the system with the share.
Disabling it makes no difference.

As regards network and server-side utilization, there are only 3 systems on
this home LAN, and only one of them is trying to map a single network drive
on this XP Home system. So there is very little going on here. I find it hard
to believe there is suddenly a resource issue.

I reviewed the first link you sent re. troubleshooting Event 2021, and I
note that this only applies to systems other than XP. Should I proceed to
follow its suggestions regardless?

Thanks.

 

[Chuck [MVP]]

Thanks Chuck.

More info: when I first tried to map this share, I got "not enough server
storage is available". So I followed this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;177078
as I have done on other systems before. With IRPStackSize set to 35 decimal,
I could now map the share. But as described, the mapped drive becomes
inaccessible within about 30 seconds, and cannot be established for some time
after that (hours possibly). Then the cycle repeats: I can map the share,
open a file or view a folder contents, then it becomes inaccessible again.

Note that even when inaccessible to the map command in Explorer, I can still
ping the "server" system, and it is able to map a file share on other XP
systems.

I am running Norton Internet Security 2006 on the system with the share.
Disabling it makes no difference.

As regards network and server-side utilization, there are only 3 systems on
this home LAN, and only one of them is trying to map a single network drive
on this XP Home system. So there is very little going on here. I find it hard
to believe there is suddenly a resource issue.

I reviewed the first link you sent re. troubleshooting Event 2021, and I
note that this only applies to systems other than XP. Should I proceed to
follow its suggestions regardless?

Thanks.

Well the KB article is written for server OSes. XP Home MIGHT be irrelevant
here. Or maybe XP Home is even more susceptible to the problems discussed. XP
Home is NOT tuned for being a server, it's tuned for home use.

Were you getting the "not enough server storage is available" error BEFORE you
wrote here? I have always wondered about possible consequences of increasing
IRPStackSize excessively, and maybe this is an illustration of doing that. NIS
is a known cause of the IRPStackSize problem, and I doubt that simply disabling
it would make a difference. Possibly not even un installing it may for sure
resolve the problem.

I'd go through the article anyway, and see how many tools work under XP Home,
and maybe one will give you a clue.

 

[Grundy]

I solved this problem by further increasing IRPStackSize, to 45 decimal (from
35 decimal). I guess 35 was right on the hairy edge, and was insufficient to
sustain the connection once I started to browse the mapped subfolders etc.

Thanks for your help.

 

[Chuck [MVP]]

I solved this problem by further increasing IRPStackSize, to 45 decimal (from
35 decimal). I guess 35 was right on the hairy edge, and was insufficient to
sustain the connection once I started to browse the mapped subfolders etc.

Thanks for your help.

That's very interesting variation then of the Error 1130. It's interesting,
that the KB article made no suggestion that IRPStackSize could be involved.

Thanks for the feedback.

 

[Grundy]

It was actually Event ID 2021 (not 1130).

That's very interesting variation then of the Error 1130. It's interesting,
that the KB article made no suggestion that IRPStackSize could be involved.

 

[Chuck [MVP]]

It was actually Event ID 2021 (not 1130).

Right. You saw an "Event ID 2021". The more commonly observed symptom that
leads to the IRPStackSize diagnosis is an Error 1130, or the old "Not enough
server storage is available to process this command.".
<http://networking.nitecruzr.net/2005/06/server-functionality-affected-by.html>
http://networking.nitecruzr.net/2005/06/server-functionality-affected-by.html