3 replies
by lordinfidel
1) Are you *sure*/110% positive you joined the computers to the domain. This is a very specific process. You have to go into network identification, click on properties (to rename this computer or join a domain, click properties).
Select domain, and enter the domain name of the AD domain. You will then be prompted for a username and password. Use the Domain Admin U/P. You can not use the users u/p.
If you did not do the above, then your computers are not joined to the domain.
*Hint, if in your logon box on the client systems. You see a drop down menu, but only the computer name is listed. Then you are not joined to the domain.
Also if you open up Users and Computers, and you do not see any of the systems in the computers OU. Then they are not joined to the domain.
If on you netwk ident tab it says workgroup and not domain, then you are not joined to the domain.
Because Workgroup is not the same as a Domain. The computers must be joined to a domain. Have I repeated myself enough?
2) If you set your local machines administrator account to the same password as the domain administrator account. Then pass thru authentication is happening. Make sure in the drop down menu that the domain is selected and not the local machine.
3) After checking 1 & 2, did you change the DNS properties on the client machine. Changing the DNS server to point to anything other than the DNS server that AD is using, will cause logons to fail. Also DNS must be AD integrated and allow Dynamic updates.
4) If all of that has been checked. And you still can not log on. Make sure that you can ping the server via IP. Then ping it by netbios name.
If you can't ping it, make sure XP's firewall is off. Doublt check your IP settings. Make sure that you have set the subnet in AD's Sites and Services, and assigned the subnet to the domain.
by davidg47
by lordinfidel
Make sure the computer accounts are showing up in AD. If they are not then that is the issue.
When you said "log on locally". You didn't create local accounts on the local machine and then using them to log onto the domain?
Make sure that your drop down menu in the logon to domain box is set to the correct place. You do not want to logon to the local machine. You want to logon to the domain. If your drop down is set to the machine name, the logon process is going to look at the local sam/account db for the authentication. Not the DC.
If all else fails. Remove those 2 machines from the domain. Delete their computer accounts in AD. And then rejoin them to the domain.
If it makes you feel any better. XP really sucks as bad as winME when it comes to networking/domains.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending