High Drive Mappings Not Persistent?

  • Thread starter Thread starter Grant
  • Start date Start date
G

Grant

Hi folks. My Windows 2000 Workstation system connects to a share which
contains my Outlook PST file. The drive letter is mapped to S:. When
I logon and startup Outlook, I get an error stating that the S: drive
is unavailable. When I goto Windows Explorer, the S: drive has an X
through it, but I am able to access files in that folder. In fact,
after I access the drive, I can then access my PST file by restarting
Outlook. The strange thing is that I've mapped the same share to a
lower drive letter (ie. H) and I don't have any problem accessing the
PST file when I logon using that drive mapping. Both shares were setup
to reconnect at logon.

This problem is happening on a network that I don't administer, but I'm
curious as to what setting, etc. is set so that higher drive mappings
aren't persistent like lower ones are and if there is any way around
it.

Any help appreciated.

Thanks. Grant.
 
Grant said:
Hi folks. My Windows 2000 Workstation system connects to a share which
contains my Outlook PST file. The drive letter is mapped to S:. When
I logon and startup Outlook, I get an error stating that the S: drive
is unavailable. When I goto Windows Explorer, the S: drive has an X
through it, but I am able to access files in that folder. In fact,
after I access the drive, I can then access my PST file by restarting
Outlook. The strange thing is that I've mapped the same share to a
lower drive letter (ie. H) and I don't have any problem accessing the
PST file when I logon using that drive mapping. Both shares were setup
to reconnect at logon.

This problem is happening on a network that I don't administer, but I'm
curious as to what setting, etc. is set so that higher drive mappings
aren't persistent like lower ones are and if there is any way around
it.

Any help appreciated.

Thanks. Grant.
Click to expand...

Take a look at the autodisconnect setting


http://support.microsoft.com/kb/138365/EN-US/

http://www.jsifaq.com/SF/Tips/Tip.aspx?id=0019

HTH?
 
Hi Steve. Thanks for the reply. Not quite the same thing I don't
think. The problem is that this share works fine if they connect using
a low letter (up to M: I believe.) If they use above that, the drive
shows up with an X through it when they logon and Outlook won't connect
to the PST file.

I'm curious as to why using a lower drive letter acts differently then
a high drive letter.

Thanks. Grant.
 
Grant said:
I'm curious as to why using a lower drive letter acts differently then
a high drive letter.
Click to expand...

Could it be something to do with the order in which windows restores connections
at log-on? Some sort of conflict of authentication credentials? (There is, I
believe, a limit of only one set of login credentials for any given windows to
windows client/server relationship; mapping two drives to the same server with
different credentials does not work. This appears to be enforced at the server
end, as a samba server will happily talk to me with several different sets of
login credentials active at the same time, but a win2k system fails will not
(system error 1219 - The credentials supplied conflict with an existing set of
credentials.))
 
Back
Top