Computer domain account problem

  • Thread starter Thread starter danieltan
  • Start date Start date
D

danieltan

After i created a domain controller, in the AD i added a computer
account to it in AD user and computers, but when i need to connect the
client(xp prof) to the domain , it asked for the computer account and
was not found. Which part i did wrong ? pls advise thanks

Rgds
Daniel
 
You can not simply add a computer account to AD Users and Computers, the
computer needs to be "joined" to the domain. You do that in the client
computer's System Properties/computer name - change, and select member of
domain where you type the Active Directory domain name. Also see the link
below to make sure your AD domain dns is correct and note that a computer
must point to an AD domain controller running dns with the domain zone
before trying to join it to the domain. Never list an ISP dns server as
preferred dns server for any domain controller or domain member. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382
 
Steve, does it means that the SRV record will appeared by itself in DNS
forward zone if netlogon service is enabled ? Also does the dns zone
file (forward) name have to be same as the AD domain name ? I've point
the client dns to the AD dns server. The server is pointing to itself
via the dns setting in network connection. Finally i've created the
client account in AD user and computers and set the client name to the
AD domain.

Rgds
Daniel
 
Steve, does the AD domain dns name or the dns server have to have a
valid FQDN in order for client to join the domain ?

Rgds
Daniel
 
The _srv records should show up shortly after dcpromo is done to promote the
domain controller. If not run netdiag /fix on the domain controller and
restart the nelogon service. The forward lookup zone should match the AD
domain name. --- Steve
 
You must use a fully qualified domain name for Active Directory to work
properly. Technically you may not have to with some configuration changes
but I would never recommend not using a FQDN for an AD domain. May use
"corp" for internal domains as in mydomain.corp. FYI the support tools
netdiag and dcdiag [domain controllers] can be very helpful in checking AD
configuration. Support tools are on then install disk in the support/tools
folder where you need to run the setup there to install them. --- Steve
 
Steve, thanks for help, it works already. Where can those tools be
downloaded ?

Regards
Daniel
 
Steven, another question. How come i created roaming profile in server
but when login using XP prof it doesn't create any profile ? I've
created a user profile folder in server and shared. Permission is full
control. pls advise. thanks

Rgds
Daniel
 
Back
Top