Keeping a connection to a mapped drive
I have a new Snapserver. All a Snapserver is, is a NAS (network attached storage) device. It's basically a hard drive that's attached via patch cable to my switch. I'm using Windows XP Pro with SP3 installed. I have successfully mapped say a "Z" drive to the Snapserver. The Snapserver allows all users fully access to the Snapserver, i.e. there's no security at all & that's fine with me. Here's the kicker: Everytime I turn my computer I find that that my "Z" drive is disconnected. So I have to click on My Computer, I see the "Z" drive entry and I have to click on the "Z" drive and then it connects. Furthermore I have to authenticate as well. Here are my questions: (1) How can I maintain the "Z" mapped drive? (There is no box that I can check that will allow me to automatically reconnect the "Z" drive). (2) Is there a way I can avoid authenticating every time I re-start my computer? Thanks a million.
If it is asking you for credentials ... click on "Connect using a different user name"
I guess I "assumed".... but just in case... Use your own user name after clicking on "Connect using a different user name"
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
BitsBytesandMore:
I don't think the persistent parameter is needed when you put it in a loginscript as it runs every time when you logon, but perhaps it is an idea just using the net use comm with the persistent par to see if the drive stays connected that way. Could also be a possible solution.
I don't think the persistent parameter is needed when you put it in a loginscript as it runs every time when you logon, but perhaps it is an idea just using the net use comm with the persistent par to see if the drive stays connected that way. Could also be a possible solution.
The truth is that I have 4 NAS drives attached to the network and they are all different brands and we never have this problem. I have them just mapped and that's it. But nothing ever surprises me anymore with Windows.... things that are supposed to work don't and the ones that aren't ...do...
ASKER
none
Untitled.jpg