The file location is correct for an NT login script - if you want to double-check, all you have to do is go through Net Neighborhood, browse to the server and open the Netlogon share - this is the share name of the %systemroot%\system32\repl\import\scripts folder.
Some ideas that may help: 95 workstations will not process a login script saved as a .cmd file, they will only read a .bat file as a login script. You have to be careful here because some commands that will work in a .cmd file will not work in a .bat file. For example, the /persistent:yes(no) switch on a net use command doesn't work in a .bat file and the entire line of the login script will be ignored by the 95 workstations if it's got that switch on it. Both NT and XP workstations can read either a .bat or a .cmd file.
Also, do you have one or more BDCs as well as your PDC? If so, you have to replicated the login script from your PDC to all BDCs to be sure that the script will run regardless of which domain controller validates the login. In that case, you have to put the login script in the %systemroot%\system32\repl\EXPORT\scripts folder and set up replication from the PDC to all BDCs.
If none of these suggestions helps, please post more info such as:1Do you see any error messages while the login script is trying to run, or does it just not appear to run at all? If error messages show either in the command window as the script is running or in the event log on the workstation, what are they? Have you tested all of the commands in your script by running them manually to be sure they work on each OS before putting them in the script?
Hope this helps!
