I'm running Windows NT 4.0 Server with a login.bat file to map drives for a Windows 2000 Workstation.

The problem is that when the user logs onto his machine, the dos window (where you would see the mapping), simply flashes for a second. No mapping of drives happen.

If I log onto another machine, running Windows NT, it works fine.

It's almost like the script runs too fast under Windows 2000.

Any ideas would be appreciated.

You're sure it's not mapping the drives? Windows 2000 runs NT4 logon scripts minimised!

I know the drives are not being mapped.

After logging into the Windows 2K machine (with the Win NT Server being the primary domain), I open my computer and the only drives listed are the local drives.

I'm able to map the drive manually.

I'm also able to create a local bat file of the exact contents of the login script and it works fine when I run it on the local machine in the startup folder.

It seems like a solution, but it's really not...

I need to be able to control and make changes to one login script for many users, not have independent scripts running on the users local machine.. I'm sure you understand why this would be a problem.

Thanks for your response!

Same as above except using Win XP Pro. Only when machine is rebooted will scripts not work. After login (no mapped drives), user logs off and then logs back in, the script is processed. Its almost like win Xp is blowing past NT script the first time.

I am having the same problem on 5 out of 5 systems after I upgraded them to Windows 2000 service pack 2. Anybody have any ideas. This is a problem. Also if the person maps to the PDC NETLOGON share and double click the bat file the script works fine.

Thanks for your help.