Why does unplugging the network cable disconnect a drive mapped to a share defined on the server?
V: is mapped on Server1 to \\Server1\Public
Sitting at Server1, I browse My Computer and open V:\.
I unplug the network cable and the window closes.
Any ideas why and how to allow the mapped drive connection without the network cable plugged in?
Sitting at Server1, I browse My Computer and open V:\.
I unplug the network cable and the window closes.
Any ideas why and how to allow the mapped drive connection without the network cable plugged in?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ok, how about a subst command? That would create a virtual drive to a physical drive path...
like subst f: c:\database would put your database in an effictive f: drive
like subst f: c:\database would put your database in an effictive f: drive
ASKER
That will work like a charm. Not familar with that command, so thanks for mentioning it.
I'll ask another question about this to give you some points.
I'll ask another question about this to give you some points.
No, don't do that. 2000 feels about right, as it wasn't that taxing...
ASKER
This is a demo machine that runs a fairly complex CORBA application.
In production the client app connects to a mapped drive to get config settings and access to other stuff.
Wanted to keep the demo consistent with production. First choice was to also have it connect to a mapped drive. It can't stay connected to the network because the demo server would mess up the development servers. The CORBA app is designed to self-discover other CORBA servers to share the workload.
Wanted to see if there was a quick an easy way to get aorund the problem.
Since all the files are on the demo server we'll just use an explicit path instead of a mapped drive.
Thanks again.