IT Employment

Ask something
Discussion Locked

Not connecting to network share drives.

0 helpful
5 replies

by hotbelw 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
About nine months ago, we migrated from Novell 4x platform to Windows NT. The servers are W2k and the workstations are XP Pro. Script Logic handles the drive mapping. Everything worked fine until about three months ago, when users began reporting that they don't get their share drives after login. They do however get mapped to their home drive, but this is handled through AD. The problem is intermittent and therefore hard to pinpoint. The only thing that will resolve this is restarting the PC and sometimes it takes up to ? dozen attempts. Once connected to the share drives, there is no problem until the next login. We have three physical sites all connected to the domain. The other sites are not experiencing this problem. I have 6 each 10MB hubs and 1each 100MB switch daisy chained. (I know, this is not good, but I inherited this network) I took one of the users that was experiencing the problem the most and moved their connection to the switch, but did not resolve. I?ve done a lot of research, but no leads yet. This problem is annoying and I would appreciate your ideas.

5 replies

by itctonguy

If not, consider doing this (using same file location on each server) and add the user account property 'login script' as to script file. Remember, an account will login to ANY DC that is available and if script file is not available on all DCs then there will be no mapped drives!

by rschmid1

I agree with ITC on this one. you might want to create a batch file (login script) on a disk and when the machines map dont, run the login script local and see what happens??

In your login script do you have the "/y" after the drive mappings??? Sometimes these cause a conflict and the machines will kill all mapped drives as well...

by omie

you mention that you have 6 switches and they are daisy chained so the 5-3-2 needs to be observed... Check your network topology. This produces intermitent problem..

The other thing that you need to check is on the way you configured your AD... Win2k doesn't like to have a NT as as BDC so if you have one yank it up and install a win2k ..and it it will take the dc if your present dc will have a problem.

by lukcad

I have read that "I took one of the users that was experiencing the problem the most and moved their connection to the switch, but did not resolve. I?ve done a lot of research, but no leads yet. This problem is annoying and I would appreciate your ideas. "
It's the same situation in my practice was. But I was long day lauthing after it: because some not smart user changed mask of net from 255.255.0.0 to 250.250.0.0 - and I can't anything understand till noted it. ;-)

by sendtrap

Hi, we have exactly the same problem. Microsoft suggested to update to the latest NIC drivers, but it didn't help. We are using IBM Thinkpads and Cisco network components only.
We believe that it could be a timing problem with the auto negotiate functionality between the NIC and the switch. An network trace showed that parts of the inital communication though the network is not taking place when the drives are not conneted.

This discussion is closed to new replies.