login script drives not mapping for certain users

pts.
Tags:
Networking
Tech support
I have this scenario where i have a simple working login script which just maps network drives. However for 2 or 3 of my users the login script doesn't map the drives on certain computers. In other words for the same user it works on one computer and not another; with the same operating system. any help or ideas would be greatly appreciated. Thank you in advance.

Answer Wiki

Thanks. We'll let you know when a new response is added.

What is the OS??? Desktop and Server please.
Jon

Discuss This Question: 7  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Cptrelentless
    Are you using NET USE in a batch file, VBScript, Kix or other? Have you put a remove statement in first to make sure they don't already have the drive letter mapped in their profile on the problem machine(s)? What OS are these machines? Can you manually map drives on them? Have you looked in the event logs? Is your interpreter/translater available on the machine?
    0 pointsBadges:
    report
  • PeterMac
    You havn't given us much to go on, but here are a few possibilities 1)simple conflict Drive letter already in use on these PC's. 2) Credentials conflict, if drives have ever been mapped using different username/password script will fail. 3) User permissions on these Systems, may not be able to map drives. First thing to do is check whether or not drives can be mapped manually on System, by this user. Post up results of this for further help.
    15 pointsBadges:
    report
  • Kwoodman
    sorry bout that. The Server OS is Windows NT and the workstation OS is Windows 2000. The users are able to map drives manually. For example, if I run the script itself manually after they have logged in then the appropriate drives would map. So it is not a drive letter conflict nor problem with their permissions on the particular system. Any further ideas would be appreciated. Thanks
    0 pointsBadges:
    report
  • scottbr
    Are you using wireless adapters for network connectivity in the workstations in which the drives will not connect? Are you sure the logon script is running? Have you tried to insert a pause statement after each line in the script to see any errors are produced?
    0 pointsBadges:
    report
  • PeterMac
    Thanks for posting back info, it always helps. Are you mapping drives dependant on User Credentials ? e.g. Z: -> ServerUsers"UserName" Have heard of problems where drives are mapped dependant on Login User, Windows can fire off the Login script before Login has actually completed, and mapping will fail in this case. Seem to remember seeing a script to pause mapping until after Login was complete, and Environment variables set up.
    15 pointsBadges:
    report
  • Onamission
    Sounds like your workstations "fell" out of the domain to me. I'd try removing one of the suspect workstations from the domain then add it back. j
    0 pointsBadges:
    report
  • Sonotsky
    Does it happen every single time the user logs in? If so, I would suspect that either one machine is not part of the domain (or is not properly establishing the connection to the domain), or something on that one particular workstation is denying mapped drives. You may have to do some serious Googling for that. I did have a smiliar issue at my last employer; domain controllers were all NT4 and workstations were XP. Occasionally/sporatically, and on the same and different workstations, some or all login-script-defined mappings would not happen. A log-out-log-back-in usually restored the mappings. However, there was one workaround that worked 99% of the time; put a text file in the root directory of the user's "home directory" mapped drive, called "personal.scr" and in that file, type in all the mappings (I can't recall off the top of my head, since I wasn't allowed to take my file with me, but I think each line had the format of "use x: servernamesharename"). The only catch was that if the DC didn't map your home drive, you were pooched. Good luck!
    695 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following