Can't add computer into domain

[djpingpong]

Sometimes I really don't understand Microsoft and it pisses me off.

I want to do something "supposedly" very simple, but for some reason it isn't letting me.

Like the title suggests, I am running a 2000 domain (wweld.com) at work... there's always been 1 computer that has been outside the domain (mainoffice)

Now, I was trying to get *mainoffice* into the domain. So, I did the following:
I changed the workgroup to domain... i typed "wweld.com" and I made sure that the primary DNS suffix was correct...
It was simple.. it accepted.. it said "welcome to the domain" ... GREAT!!! I restarted and I tried to login to "WWELD" and it tells me that I cannot login to the domain...

Now, I even tried to add a "Computer" in the Active Directory name "mainoffice"... but it still wouldn't recognize...

Is there a few steps that I missed along the way? This is irritating... can somebody help please?

 

[pgaliardo]

I think there was s similar post recently. Check your DNS settings on the machine you just joined to the domain. Make sure it points to your Active Directory DNS server, not the DNS of an ISP. I've heard of incidents where the wrong DNS was on a workstation and the workstation was able to join a domain, but the user was then unable to logon.

 

[djpingpong]

No.. it's not the DNS setting.. it's definitely pointing to the right place because it's all handled by DHCP on the domain controller.

 

[pgaliardo]

After reading your post again, had a few other thoughts. You said you got the welcome message when joining the domain. But in Active Directory Users and Computers, there is still no account for the "mainoffice" machine? How many DC's are in the domain. Perhaps it is just a replication problem?

When you go to logon, you have 3 lines in the logon box, User, Password and Domain, correct? And in the pull-down box for domain, your domain is listed there?

One other thought, are you trying to log on with the same local user account that you always used to log onto that machine, or are you using a valid domain user account?

 

[djpingpong]

I think you're onto something here...

I have 2 domain controllers... and maybe I haven't replicated it yet. But how do i do that?

Secondly, the accounts that i'm using is a valid domain user account because i've tried it with other computers in the domain.

 

[pgaliardo]

I forget if there is a way to force replication. Maybe someone else can help out here.

I would look in AD Users and Computers on each domain controller and see if you there is a computer account for the new machine on either DC. If there is on 1 and not the other, my guess would be that it didn't replicate yet and the computer is trying to log into the second DC.

 

[Cstorms]

Not that I have any valid knowledge behind this idea, but couldnt you setup the dns settings to point to the "primary" dc that sends out the replicated data if indeed that is the case so that you can test to see if that is the problem?

 

[markdmac]

I would first make sure that DNS is configured properly.
[blue]
DNS Settings:

Configure the server NIC to only list itself or other DCs, no ISP DNS gets configured on the NIC TCP/IP properties.

In DHCP, set the DNS scope option to only provide the IP of your local DNS server

For any statically configured IPs, make sure the DNS only lists local DNS servers and not ISP DNS.

In the DNS snap-in on the forwarders tab enter your ISP DNS.
[/blue]

If that is not the problem then check both DCs to see if the machine account exists. If the account exists on one server but not the other and more than 15 minutes has passed then you have a replicaiton issue. THe first step in troubleshooting a replicaiton issue is to verify that DNS is setup as I have indicated above, so check it even if you are sure it is OK. Next steps in trouble shooting replicaiton is to run DCDIAG and NETDIAG on each server.

You can attempt to force replicaiton in AD Sites & Services.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

 

[dberg35]

Also make sure each server that is doing DNS is pointing to eachother. Also did you try to add another to rule out only that PC? Also is it running XP Pro SP2, if so turn off the firewall. I have had the firewall interfere before.