Solved

Computer is member of domain, doesn't run login script - can't see server drive

Posted on 2009-05-04
3
280 Views
Last Modified: 2013-12-23
We have 6 computers hooked up to a server. Each computer runs XP Pro SP3. The server runs SBS 2003. Each computer runs a login script that makes the server drives accessible (we have a shared "T" drive that is shared by everyone and we each have a "X" drive where we put our own information). When the computer logs onto the domain, it runs a script in the command box that initializes these drives. I was forced to wipe one of the computers out and reload everything on from scratch. The user information was left unchanged on the server, so i'm sure everything is setup right no the server side. I added the user to the domain.  I'm not sure how I added the user (it was a couple of weeks ago), but everything seems to be fine, except this issue.

I'm not sure what else you need. Please let me know if you need any other info.

Thanks in advance,

Dean
0
Comment
Question by:chandldj
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 14

Expert Comment

by:dmwynne
ID: 24298384
Did you give the computer the same name it previous;y had?  If you so you need to reset the AD account before rejoining to the domain.  If you did not reset it you'll need to remove it from the domain, reboot, reset computer account, join the computer back to the domain.
0
 
LVL 13

Expert Comment

by:usachrisk1983
ID: 24298392
If the user logs into another computer, does it work?  If someone else logs into the problem computer, does it work for them?  This will tell you/us if it's a computer or a user problem.

Where does the login script run from for your other users?  If it's part of the user object (the login script parameter), make sure that it exists for the user having the problem.  If it's through a policy object, make sure the user and computer are in OUs that are assigned the policy (depending on if it's a login script or a startup script).


0
 

Accepted Solution

by:
chandldj earned 0 total points
ID: 24305969
The answer was this...

When I joined the computer to the domain, I used wireless networking. The computer was connecting to the network through wireless. I needed to logon to the computer once with a wired connection. Then the drives were put onto the computer. Afterwards, it was ok to go back to a wireless connection.

Thank you all for your help.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question