Discussion Locked

Not seeing network drives after login

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have resently being getting calls for users, that they are logging in, but are not seeing the network drives. The login scripts are not appearing at login either. We have made no changes to the sever. I doesn't effect everyone or is it constant. We have checked everything we can think of and are at a loss. Any help would be greatly appreciated.

7 replies

by jpoandl

Seeing how the problem is not consistant, I think you should start trouble shooting this by examing your domain controllers. If you have more than I domain controller in your environment, a user can be validated by more than one server. If there is a problem with only one out of say 5 domain controllers, the problem will not be experienced by your whole company. Rather, the problem will seem non-sonsistant. From you description, I think this senerio applies to you.

I would first perform a routine check of all of your domain controllers. Check to make sure that all the AUTOMATIC services are started. What type of logon scripting are you using (KIXTART is very popular.)? Make sure KISTART service is started if you are using it on all DC's. Check the event viewer of each server.

I would then check the NETLOGON directories of every Domain Controller. The NetLogon directory holds the NT logon scripts that can automatically map network drive for the user. Make sure that all NETLOGON directories are the same. For example, in a basic configuration, all of your NETLOGON directories should contain the exact same files.

Also, are you using NT REPLICATION to synchronize the netlogon directory? If so, maybe there is aproblem with the replication?

Anyway, I hope I gave you some ideas....I think you should provide some more detail to your problem. Maybe we could help a little more....thanks.

by frobo

Hi,

this happens if someone has installed a new Server (BDC) and doesn?t copy the files of the netlogon folder to the new server.
The Netlogon share is located at \system32\repl\import\scripts.
This could happen if the user?s authentifcation is made over WAN, this is somtime a problem why such things happens.
The first thing i would look for is the variable logonserver in a cmd-window. Is the Server in my LAN or it?s somthing elsewhere ?
If so, the you must use som tools of the Reskit for such issues.

Hope it helps

Frobo

by timber

Yup It sounds like a replication problem. I would suggest not using NT's replication service. I would write a small batch file that copies the scripts to the netlogon directory of each BDC. Winnt\system32\repl\import\scripts\(Login.script). Thisway everytime you modify the login script you know that all you need to do is run the batch file and the updates are complete.

I have had several problems trying to use replication. I have had about a 50 50 chance of making it work.

Hope that helps....

This discussion is closed to new replies.