Server 2003 mapped drive disconnects from SAN

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



We have a Windows 2003 SP2 server with mapped drives to another 2003 server
with SAN shared drives.
The mapped drives periodically disconnect from the shares and cannot be
reconnected without either rebooting the server then clicking the drive and
entering the credentials, or deleting the mappings then re-creating them and
entering the credentials.

The mappings in question are established using credentials other than those
of the current logon.
I know that Server 2003 SP1+ no longer caches credentials when you map using
a different user name.

I suspect that when the connection is first established and the credentials
passed, the SAN server is setting up some time limited session for that
connection and that once the time limit is exceeded the only way to
re-connect is to re-authenticate but since the application server cannot
cache the credentials this cannot happen.
Is there a setting on the SAN server that can either disable the time limit
or expand it further so the disconnects will happen less frequently? This
is not the 15 minute timeout for closing out an inactive connection, that
occurs also but the connection comes back as soon as it is accessed.
Any idea what the time limit on this connection might be?

Two of our production servers lose their connections to these drives a
couple times a week though I have not yet been able to predict when it might
happen. It brings down our print production system until someone can
disconnect and re-map the drives and this often happens in the wee hours of
the morning when our print activity is at it's highest point.

Other mapped drives to other servers do not have this problem, only the
drives to the SAN share space.


.



Relevant Pages

  • Re: Add new cluster and use existing LUNs?
    ... Even a SAN has a maximum I/O capacity. ... you can share a LUN with more than one server. ... Microsoft SQL Server MVP ... > The first 5 drives of our SAN share the system binaries, ...
    (microsoft.public.sqlserver.clustering)
  • Re: How does a SAN connect to a computer?
    ... A Storage Area Network, or SAN, is a specialized chassis that holds a disk write controller and a bunch of hard drives. ... Kind of like a blade server requires a special chassis to hold the blades, and provides backplane communications between them, the SAN chassis holds 12-16 hard drives, the write controllers, power supplies, and provides a backplane for communications between them. ...
    (borland.public.delphi.non-technical)
  • Re: How does authentication work?
    ... I can only guess as to the authentication. ... I have no idea how the SAN shares are setup and do ... The connection does not drop every day and it is hard to tell when it occurs ... Our application server has 10 drive mappings. ...
    (microsoft.public.windows.server.general)
  • Re: Add new cluster and use existing LUNs?
    ... > Even a SAN has a maximum I/O capacity. ... you can share a LUN with more than one server. ... > Microsoft SQL Server MVP ... >> The first 5 drives of our SAN share the system binaries, ...
    (microsoft.public.sqlserver.clustering)
  • Re: How does authentication work?
    ... This I believe is because 4 drives ... the connection fails all 4 drives have to be deleted before any can be ... is the remote server that requests the credentials to authenticate the ...
    (microsoft.public.windows.server.general)