DC troubles...

[bhb3881dmb]

I have a domain controller that won't let me join any machines to the domain. I removed one system, and tried to put it back, but it won't let me.

Anyway, I want to DCPROMO my Exchange server to be the DC, then trash the old DC.

The old DC seems to be the reason I can't join the domain, so if I do DCPROMO, does this just copy the AD and all the users, or does it do other deep down things to the OS?

Thanx

 

[hewissa]

Copies the AD structure, scripts - basically makes it an equal among the other DC's. Make sure you move your FSMO roles to the new DC before demoting the old DC.

What is the error your getting thats not allowing the other machines to join? What is the structure of your domain,DNS, WINS,DHCP... Hewissa

MCSE, CCNA, CIW

 

[bhb3881dmb]

OK, here goes,

select domain, enter domain name
click OK

Get the challenge/response box,
enter username & PW

Error:

Network Identification (box title)

The following error occurred attempting to join the domain "MYDOMAINNAME"

The network name cannot be found.

I can ping the machine with system name.

When I try to map a drive, I get the following:

The network path \\mymachine\c$ could not be found.

Thanx,

Bruce

 

[hewissa]

Is DNS running? Can you map \\computer_ip\share?

Sounds like DNS errors. What does your Event Viewer show? Hewissa

MCSE, CCNA, CIW

 

[bhb3881dmb]

Hi Hewissa,

Which parts of FSMO?
To seize the domain naming master role
To seize the infrastructure master role
To seize the PDC emulator role
To seize the relative ID master role
To seize the schema master role


Here are some logs to look at, I'm sure they tell the story:

4/10/2003 9:42:15 AM DNS Information None 2 N/A MYDOMAIN The DNS server has started.
4/10/2003 7:47:46 AM DNS Error None 4000 N/A MYDOMAIN The DNS server was unable to open Active Directory. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code.
4/10/2003 7:37:46 AM DNS Warning None 9999 N/A MYDOMAIN The DNS server has encountered numerous run-time events. These are usually caused by the reception of bad or unexpected packets, or from problems with or excessive replication traffic. The data is the number of suppressed events encountered in the last 15 minute interval.


Thanx,

Bruce

 

[bhb3881dmb]

Sorry I forgot....

That last log was the DNS log, this next one is the system log:

Type Date Time Source Category Event User Computer
Warning 4/10/2003 4:23:46 PM Print None 2 Administrator MYDOMAIN
Warning 4/10/2003 4:23:14 PM Print None 20 SYSTEM MYDOMAIN
Warning 4/10/2003 2:58:51 PM W32Time None 11 N/A MYDOMAIN
Warning 4/10/2003 12:43:06 PM W32Time None 11 N/A MYDOMAIN
Warning 4/10/2003 11:12:36 AM W32Time None 11 N/A MYDOMAIN
Warning 4/10/2003 10:27:21 AM W32Time None 11 N/A MYDOMAIN
Error 4/10/2003 9:42:44 AM Service Control Manager None 7031 N/A MYDOMAIN
Information 4/10/2003 9:42:43 AM Application Popup None 26 N/A MYDOMAIN
Information 4/10/2003 9:42:41 AM Wins None 4097 N/A MYDOMAIN
Warning 4/10/2003 9:42:06 AM W32Time None 11 N/A MYDOMAIN
Error 4/10/2003 9:41:59 AM Service Control Manager None 7024 N/A MYDOMAIN
Error 4/10/2003 9:41:58 AM Service Control Manager None 7000 N/A MYDOMAIN
Information 4/10/2003 9:41:33 AM Browser None 8015 N/A MYDOMAIN
Warning 4/10/2003 9:41:29 AM NetLogon None 5781 N/A MYDOMAIN
Information 4/10/2003 9:41:21 AM Browser None 8015 N/A MYDOMAIN
Error 4/10/2003 9:40:30 AM server None 2506 N/A MYDOMAIN
Information 4/10/2003 9:39:38 AM eventlog None 6005 N/A MYDOMAIN
Information 4/10/2003 9:39:38 AM eventlog None 6009 N/A MYDOMAIN
Information 4/10/2003 9:36:37 AM eventlog None 6006 N/A MYDOMAIN
Error 4/10/2003 9:36:14 AM DCOM None 10010 SYSTEM MYDOMAIN
Error 4/10/2003 9:34:55 AM DCOM None 10010 Administrator MYDOMAIN
Error 4/10/2003 8:09:43 AM DCOM None 10010 Administrator MYDOMAIN
Error 4/10/2003 8:09:13 AM DCOM None 10010 Administrator MYDOMAIN
Error 4/10/2003 8:08:47 AM DCOM None 10010 Administrator MYDOMAIN
Error 4/10/2003 8:03:56 AM DCOM None 10010 Administrator MYDOMAIN
Error 4/10/2003 8:02:58 AM DCOM None 10010 Administrator MYDOMAIN
Error 4/10/2003 8:02:49 AM DCOM None 10005 Administrator MYDOMAIN
Error 4/10/2003 8:02:49 AM Service Control Manager None 7001 N/A MYDOMAIN
Error 4/10/2003 8:02:49 AM DCOM None 10005 Administrator MYDOMAIN


Thanx, Again

 

[steveNY]

You may have DNS configuration problems.

Review the KB article Q260371 for tips on correcting possible problems.

Basicly,
Ensure our Zone is configured for Dynamic Updates
Run Netdiag /fix on your DC
Stop and Start the netlogon service to re-registrer the server

 

[hewissa]

The DCOM error you can ignor.

What service pack is installed, I found this article refering to your log post. In a nut shell it says install the latest service pack.

http://support.microsoft.com/default.aspx?scid=kb;en-us;258072

As for FSMO, if there are any on the DC you want to demote, I would move those. How many DC's?

Have a look at this article regarding DNS:

http://www.microsoft.com/technet/tr...indows2000serv/reskit/tcpip/part2/tcpch06.asp

If you are have such problems with your DOMAIN, running dcpromo on the exchange would probably fail since the DNS and AD is not in sync. Or it would create a further instability in your network. Hewissa

MCSE, CCNA, CIW

 

[bhb3881dmb]

I am running SP3

only 1 DC

Thanx

 

[bhb3881dmb]

I got 2 errors when I ran NETDIAG:

DC list test . . . . . . . . . . . : Failed
Failed to enumerate DCs by using the browser.
[NERR_BadTransactConfig]


Trust relationship test. . . . . . : Skipped

Thanx

 

[bhb3881dmb]

OK, I'm slow, but I found the problem with this.

For some reason, the 2 connectors needed for comm. did not get started, I did

net start IPC$
net start ADMIN$

Now I can join the domain and all is well.

Thanx,