Mapped file share unavailable within seconds
in [Network and Web]
|
Prev: .rra files??
Next: Map network drive
From: Grundy on 8 May 2008 21:46 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.
From: Chuck [MVP] on 9 May 2008 01:27 On Thu, 8 May 2008 18:46:00 -0700, Grundy <Grundy(a)discussions.microsoft.com> wrote: >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. -- Cheers, Chuck, MS-MVP 2005-2007 [Windows - Networking] http://networking.nitecruzr.net/
From: Grundy on 9 May 2008 07:12 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.
From: Chuck [MVP] on 9 May 2008 20:21 On Fri, 9 May 2008 04:12:00 -0700, Grundy <Grundy(a)discussions.microsoft.com> wrote: >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. -- Cheers, Chuck, MS-MVP 2005-2007 [Windows - Networking] http://networking.nitecruzr.net/
From: Grundy on 9 May 2008 20:55
It was actually Event ID 2021 (not 1130). > On Fri, 9 May 2008 04:12:00 -0700, Grundy <Grundy(a)discussions.microsoft.com> > wrote: > > >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. > |