|
Question : Missing Network Drives
|
|
I have a question,
We have an intermittent problem with missing network drives. The problem has gotten worse when we rebooted the Servers over the weekend. Sometimes the logon process does not map 2 or 3 drives after a long delay and these drives point to a Microsoft Server.
Although the drives are mapped via Active Directory, including the NetWare ones, the ones that are usually missing point to Microsoft Servers.
I would like to point out that we have been getting around the problem by rebooting the workstations several times.
Our environment is a mixed NetWare 5.1 and Active Directory with the following configuration
1. Netware client flavors ranging from 4.83 to 4.90 SP2.
2. Windows XP Pro SP1
3. NIC Card configured to Auto Detect duplex speed, so as the router.
3. Domain Controllers are Windows 2003 SP1
4. Logon Scripts are running from Active Directory via Group policy. Novell Scripts are disabled. Users require accessing a NetWare Server but the mapping is done via Active Directory Script.
Any ideas?
Thanks
|
Answer : Missing Network Drives
|
|
It could be a replication problem. That sounds a little weird at first I know, but it has happened to me.
Check the SYSVOL folders on each of your DC's and make sure that all of the scripts are there. It could be that some sort of replication issue is keeping the script from populating to the other DC's. That would explain why sometimes is works, and sometimes it doesnt.
Rebooting the station several times could cause the client to hit a different DC, one that has the script.
Probably not your problem, but worth a look.
Good luck!
|
|
|
|