I've used a startup script to map network drives, however when a user logs in the drives are displayed as diconnected even though you can browse through them.
I've tried what you suggested but it didn't make any difference.
Would the fact that the share the drive points to is a DFS share make any difference?
I get this every now and then, we use a login script to map the drives. To be honest I think its just a little windows bug
Its sometimes worth if this is a script to REMOVE the mapping first then re map the drive (all in the script)
It's probably because you cannot give machines access to shares, but only users. Why are you running this as a startup script and not a login script?
It's quite common that users in different OUs have different network drives, so it makes sense to create drives on a per user basis and not per computer.
I think he means when he logs on they are mapped but inform him they are disconnected, when he tries to access one he can without any problems.
Try running the script as a logon script, or even disconnecting the drives while logged on as a user, then running the script manually and see if you get the same results.
If it is a batch file you could set it to switch to the newly mapped drive in the script which would attempt to access it and hopefully open the connection automatically.
Code:net use s: \\server\student s: net use .....etc
I get that all the while aswell. I assume its because it loses the connection for a split second. It doesnt keep alive if you like.
Hasnt really bothered us as it works reguardless.
There are currently 1 users browsing this thread. (0 members and 1 guests)