Mapped Drives 'drop in the middle of the night'

  • Thread starter Thread starter Dan K
  • Start date Start date
D

Dan K

The following occurs only for one user (Domain Admin). The following
recently started (last week or so). The Domain Admin (Administrator) is
log-on for 3 servers (2 W2k Server and 1 W2003 Server). The following occurs
only on the W2k Servers.
There is a log on script which has several NET USE mappings to various SNAP
4000 and Window server Shares (Including Share1, which Domain Admins group
has Full Access to - Just verifyied).
When I log on as Admin, as expected, access is there...throughout the day, I
can access.
However, when I come in in the a.m., all of the SNAP drive mappings
(including Share1) respond with
*network drive*:\ is not accessible. Network Access is denied.
The W2K shares are still assessible.
The drops only occur on the W2K servers...no such issue on the 2003.
The same occurs if I try to manually map, or browse network neighborhood.
However, if I log off and log back onto the server, all is well.
I can not find anything within event log or Snap log as to what or when this
access precisely drops.

Is there any decent explaination on how mappings work, or any settings in
which I can see when the mapping drops.
Any ideas? Thanks, Dan
 
Dan said:
The following occurs only for one user (Domain Admin). The following
recently started (last week or so). The Domain Admin (Administrator)
is log-on for 3 servers (2 W2k Server and 1 W2003 Server). The
following occurs only on the W2k Servers.
There is a log on script which has several NET USE mappings to
various SNAP 4000 and Window server Shares (Including Share1, which
Domain Admins group has Full Access to - Just verifyied).
When I log on as Admin, as expected, access is there...throughout the
day, I can access.
However, when I come in in the a.m., all of the SNAP drive mappings
(including Share1) respond with
*network drive*:\ is not accessible. Network Access is denied.
The W2K shares are still assessible.
The drops only occur on the W2K servers...no such issue on the 2003.
The same occurs if I try to manually map, or browse network
neighborhood. However, if I log off and log back onto the server, all
is well.
I can not find anything within event log or Snap log as to what or
when this access precisely drops.

Is there any decent explaination on how mappings work, or any
settings in which I can see when the mapping drops.
Any ideas? Thanks, Dan
Click to expand...

try looking here

http://support.microsoft.com/default.aspx?scid=kb;en-us;138365

hope that helps

Regards
 
Steve, thanks for the link...at least it puts a name to the problem! I
logged onto the servers with a different account, and it did the same thing
last night for the same type of shares...so it definately appears to be
within the 2000 server OS...have to say...SNAPS are cheap and reliable
storage (have had current for 4 years), but it can be a pain in the ass when
it comes to stuff like this...

Will let ya know. Again, appreciate the tip. Dan
 
Dan said:
Steve, thanks for the link...at least it puts a name to the problem! I
logged onto the servers with a different account, and it did the same
thing last night for the same type of shares...so it definately
appears to be within the 2000 server OS...have to say...SNAPS are
cheap and reliable storage (have had current for 4 years), but it can
be a pain in the ass when it comes to stuff like this...

Will let ya know. Again, appreciate the tip. Dan
Click to expand...

glad to have been of help Dan
 
Back
Top