Mapped file share unavailable within seconds
in [Network and Web]
|
Prev: .rra files??
Next: Map network drive
From: Grundy on 6 May 2008 22:09 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.
From: Grundy on 6 May 2008 22:32 "Grundy" wrote: > 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.
From: Anteaus on 8 May 2008 04:07 A possibility: http://mylogon.net/support/psave "Grundy" wrote: > 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
From: Grundy on 8 May 2008 06:47 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). "Anteaus" wrote: > > A possibility: > http://mylogon.net/support/psave > > "Grundy" wrote: > > > 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 >
From: Chuck [MVP] on 8 May 2008 14:15
On Tue, 6 May 2008 19:32:03 -0700, Grundy <Grundy(a)discussions.microsoft.com> wrote: > > >"Grundy" wrote: > >> 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. 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/articleid/76666/jsi-tip-5362-how-do-i-troubleshoot-event-id-2021-and-2022.html> http://windowsitpro.com/article/articleid/76666/jsi-tip-5362-how-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 -- Cheers, Chuck, MS-MVP 2005-2007 [Windows - Networking] http://networking.nitecruzr.net/ |