timgreen7077
asked on
Windows 2003 Server
I have a win2003 server with AD, and I also have a laptop that is not a member of the domain. On the server I have a shared folder called movie backups, and I log into this folder from my laptop by entering my network credential in My Network places. The laptop is on a work group. My question is:
Is there a way to close the network connection to the shared folder when I'm done, without having to log off my laptop or restart it? Once I close the connection I would like to be prompted to login again, and use a different user credential if I choose, but as it stands now, once you log in, you are always logged into that shared folder until you log off the computer. The laptop is win xp pro. I even closed the connection on the server in File Server Management, but the connection remains. I tried:
net use \\192.168.1.10\backup movies /delete
and i get an error : The network path was not found. Any help would be great!
Is there a way to close the network connection to the shared folder when I'm done, without having to log off my laptop or restart it? Once I close the connection I would like to be prompted to login again, and use a different user credential if I choose, but as it stands now, once you log in, you are always logged into that shared folder until you log off the computer. The laptop is win xp pro. I even closed the connection on the server in File Server Management, but the connection remains. I tried:
net use \\192.168.1.10\backup movies /delete
and i get an error : The network path was not found. Any help would be great!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You might try Computer Management Console (right click computer, manage) and look at shared folders and open sessions.
You might try in Explorer, Alt, Tools, Disconnect Network Drive..., where you should see \\machine\sharename connections even if there is NOT a mapped drive letter.
However, depending what program has files via network open, some programs interpret that as comm loss and promptly re-open the connection.
As you've likely surmised, in my experience, worse, your connection to any given machine can't be two different credentials simultaneously, so connect to machineA\shareA as domain\user1 you generally cannot then also connect to machineA\shareB as domain\user2 as much as you may try going through the motions to connect with "different credentials" (as it is called in the map network drive dialog screen of XP clients)
The "classic" problem is when printer connections are made as guest and then no matter how hard they try they cannot connect to a share as themselves because they're already connected to a printer on the same server machine "as guest".