Discussion Locked

LOGIN SCRIPT PROBLEMS?

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have an NT 4 Domain and a client running Windows 95 has problems logging in.
When she logs in it runs the same login script the same as everyone else which basically just runs "net use" statements to map drives to shares on the network.
Most drives map fine but a few don't map at all, she then has to logout and login again so the login script runs a 2nd time and all the mappings work fine then.
Any ideas? I've tried deleting her login script batch file and replacing it with another user who has no problems but its still the same!

11 replies

by tduval

Did you double checked the w95 syntax for the command NET USE ?
Many changes from OS to OS, not always easy to find.
For example, the /persistent changed from NT to w98, and other.
Give use you script example, to check also.
And did you tried tomanually run script ? Did you increased space given to SET assignments ?

by mozster

Script attached as requested, we don't use any SET commands.

net use r: \\gha_server\csaurora
net use g: \\aberdeen\group
net use t: \\aberdeen\timesht
net use v: \\aberdeen\virusdef
net use p: \\aberdeen\sandram
net use j: \\aberdeen\boardnet use w: \\aberdeen\ghaweb
net use x: \\gha_server\sandram

by sgt_shultz

this sounds like network connectivity issue to me. second time around, she is talking ok on the network, so drive mappings work...i would try her with another NIC, or another network jack or see if she has NIC media type set to 'autosense', if so, then try lock the media type on her NIC either down to 10MB half duplex or up to 100MB full duplex and see if that helps. meanwhile, you could 'cheat' and add part at beginning of script that just attempts to 'net logon' to the computers you are mapping drives from...maybe it will sort out the login/connectivity issues at that time and let the mappings work...

by sigmapi71

What error does "NET USE" outputs? Maybe something related to name resolution? If so try adding in c:\windows\system\hosts IP address and name of the problem server. Hosts file is a text file without extension and the syntax is:
ip address [TAB] hostname
One name in each line.
Good luck.

by neos

I agree with the previous answer... I think a host file is going to be the best option for you

by mozster

Have tried adding in a HOSTS file as suggested but still have the same problem unfortunately!
The client does use WINS and has addresses in for both a primary and secondary WINS server.
Is it possible its someting in the WINS manager on the NT servers?

This discussion is closed to new replies.