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

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
chandldjAsked:
Who is Participating?
 
chandldjConnect With a Mentor Author Commented:
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
 
dmwynneCommented:
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
 
usachrisk1983Commented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.