Mapped Drives unavailable until browsing to drive in Open dialog.

[jeolmeun]

I have a couple of programs that are unable to access or cannot view
files on a network folder mapped to a drive. The programs are able to
access the mapped drives after I do a File Open and browse to the
drive by typing X: in the path.

For example, if I have X: mapped to \\192.168.1.123\Documents and one
of the programs will fail if a script tries to open a file from X: at
X:\SomeFile.ext. I would have to do File | Open and navigate to X:\ by
typing X: and enter. Then I would cancel the Open dialog. The program
will successfully open the file if I try it afterwards.

This happens in more than one application. This is on a Vista Ultimate
32-bit with a drive mapped to an XP folder accessible over the network.

 

[Guest]

I'm using Vista Business here, I see the odd drive dropped on occasions, but
then this is a large network. Its not something i would expect to see, but
like you just double clicking on the drive activates it again.

The only suggestion I can make is to re-create the mapped drive and ensure
that it the check box "re-connect at logon" is selected.