Link to home
Start Free TrialLog in
Avatar of comtekso
comtekso

asked on

2003 login problems

I have a single server running 2003. It is a fresh install. I have a mix of work stations... win98, win2k, and XP Pro. some, but not all, of my Win2k and XP work station can not login. I get a message that says the domain can not be reached or account information in not valid. If I log in as Admin to the local machine and explore the workgroup I can see the server and even attach to it using different domain login names. Why is this? Why can I not log directly into the domain but I am bale to attach to the server thru the workgroup?
Avatar of comtekso
comtekso

ASKER

Also I am not sure if this is related, but I have a simple login script that maps a drive(login.bat) and it does not run upon login. Where should this login.bat file be located on a win2003 server?
is all your workstations on the same subnet?
Yes. They are all on the same sub-net. Nothing on the workstations have changed. I previoulsy had a Win2k server and I did a clean install of Win2003 on it.
Your LOGIN.BAT file should be in your NETLOGON directory: ie. \\SERVERNAME\netlogon
It's located in C:\WINDOWS\SYSVOL\SYSVOL\DOMAINNAME\SCRIPTS.

When you say FRESH install... what does this mean? Upgraded your current Machine to W3K server or introduced a new server into the AD?
When you try to add the machine to the DOMAIN from the LOCAL admin login,what is it saying to you?
I didn't have to change the domain, maybe that is my problem.

My Win2k server HD crashed, so I installed new HD's in the server and installed Win2003 and gave it the same domain name as before. I have not changed anything on the workstations. I set 2003 with the same DHCP scheme.
ASKER CERTIFIED SOLUTION
Avatar of Lazarus
Lazarus
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I had to disjoin the domain and reconnect. Once I did that I could log in however it created a new profile on the workstation so I had to do some creative copying of the original profiles.