DCDIAG and Global Catalog issues - Replication

Hi Experts.

A couple weeks ago, my main ad computer failed. I (with experts help) got it running again. I wanted to make sure my other server was a GC and did so by checking the proper box. WHen I checked later to make sure it worked, this is what I got.

I am getting errors when I tried to make a second server in my domain a GC. I attached a copy of the dcdiag. I am not sure what to do to fix this. My DNS seems to be fine.

I know you will require more information, so just ask.

Thanks

G


dcdiag.txt
Plaintree_SystemsAsked:
Who is Participating?
 
Darius GhassemCommented:
Just put  the D4 and D2 flags this should create the sysvol.

http://support.microsoft.com/kb/315457
0
 
Darius GhassemCommented:
Check replication because you are having issues with this.

http://support.microsoft.com/kb/297230
0
 
Plaintree_SystemsAuthor Commented:
Thanks - I realize that I am having replications issues. Hence the post. I am wondering how to fix the dcdiag issues that are apearing in the txt file.

0
WEBINAR: 10 Easy Ways to Lose a Password

Join us on June 27th at 8 am PDT to learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees. We'll cover the importance of multi-factor authentication and how these solutions can better protect your business!

 
Darius GhassemCommented:
Use ReplMon.exe to check for replication.
0
 
Plaintree_SystemsAuthor Commented:
it is showing that replication is fine
0
 
Darius GhassemCommented:
What errors are you getting in the Event Viewer under FRS?
0
 
Plaintree_SystemsAuthor Commented:

I am gettting warnings - event 13508

The File Replication Service is having trouble enabling replication from W2K3SVR to W2K3SVR2 for c:\windows\sysvol\domain using the DNS name w2k3svr.Hypernet. FRS will keep retrying.

I tried to follow the steps through without much luck.
0
 
Darius GhassemCommented:
So, as you can see you are having replication problems. Looks like you are having DNS issues. Post ipconfig /all.
0
 
Plaintree_SystemsAuthor Commented:
Okay - Thanks for the quick reply and ongoing help.

Here is the ipconfig /all for both servers.


Server # one - w2k3svr

   Host Name . . . . . . . . . . . . : w2k3svr
   Primary Dns Suffix  . . . . . . . : Hypernet
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : Hypernet



Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-30-48-80-59-5E
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.0.0.100
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.0.2
   DNS Servers . . . . . . . . . . . : 127.0.0.1
                                       10.0.0.99



Server 2 - W2k3svr2

   Host Name . . . . . . . . . . . . : w2k3svr2
   Primary Dns Suffix  . . . . . . . : Hypernet
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : Hypernet

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II GigE (NDIS
 VBD Client) #2
   Physical Address. . . . . . . . . : 00-1E-4F-34-5B-A2
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.0.0.99
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.0.2
   DNS Servers . . . . . . . . . . . : 127.0.0.1
                                       10.0.0.100

0
 
Darius GhassemCommented:
Remove 127.0.0.1 put the actual IP address not the loopback. Run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix.
0
 
Plaintree_SystemsAuthor Commented:
okay - did that to both machines. Now we wait?

 How come you use the actual IP instead of a loopback?
0
 
Darius GhassemCommented:
When you have more the one DC you can cause DNS issues using the loopback. MS puts the loopback in the first DC created because to allow for easier configurations for small businesses and if you forget to put the actual IP address in the settings instead of a external ISP IP address.
0
 
Plaintree_SystemsAuthor Commented:
okay - as my learning curve grows.

So is there a way to check to see if all this worked? or will it take some time to replicate through?

0
 
Darius GhassemCommented:
You can force replication by going to AD sites and services. Then run dcdiag check for errors. If you still have some then I would give it sometime.
0
 
Plaintree_SystemsAuthor Commented:
Okay - i will wait and watch for a bit - I will let you know asap. Thanks for your help.

G
0
 
Plaintree_SystemsAuthor Commented:
Morning,

The errors are still there. I attached a new copy of DCDIAG. Anything else I can try to look at?
dcdiag.txt.txt
0
 
Plaintree_SystemsAuthor Commented:
Can anyone else help me with this?

Thanks

0
 
Darius GhassemCommented:
So, you are still having major issues on the server. Your netlogon share is not present and the server is no saying it is a DC which is a major problem. Is this your old 2003 server or is it the 2008 server?
0
 
Plaintree_SystemsAuthor Commented:
Morning,

Both are 2003 servers. I did order a new 2008 server yesterday but I am afraid that when it comes in and I install it I will have the same issues.

0
 
Darius GhassemCommented:
You will have issues. Do you have a backup? Is one servr functioning properly without errors?
0
 
Plaintree_SystemsAuthor Commented:
Hi,

Yes my main sever - w2k3svr is operating without any issues. I have checked everything I know to make sure the dns is working and it seems to be okay on both systems. The main server is going to be taken offline when the new one comes in or at least thats what I am hoping to do.

0
 
Darius GhassemCommented:
Lets do this. You can demote the server that is having issues or you ca use the burflag method to try to get it working again.
http://support.microsoft.com/kb/958804

If you go with the demote route you can re-promote again after the demotion. Once you demote I would run metadata cleanup on AD you delete any lingering objects from for this DC. Also, delete any DNS records for this DC>
0
 
Plaintree_SystemsAuthor Commented:
Okay so here is a question.

Which server do I demote? My main one (which I am replacing that could be the root if the issues) or the server2 that isn't taking the replication properly?

I think the KB steps are pretty straight forward and I will see if I have a vaild backup first. I will try that before I demote as that will require users going offline for a while or a weekend.

can I run metadata cleanup on both servers to clean them up? (without demoting them?)

0
 
Darius GhassemCommented:
No, you only want to run metadata on AD to remove lingering objects on DCs that are no longer present on the network.

You want to demote the server having issues with replication.

I would actually try the burflag before restoring anything.

Demotion shouldn't affect your users.
0
 
Plaintree_SystemsAuthor Commented:
Okay - I will try the burflag first. I do see an old dc (before my time). It shows up under AD sites and is no longer in exsistance. That is on the main server.

My new server just arrived today. My plans are to replace my main one (it is old) but want to make sure that my second server is replicating properly first.

I will get to work and let you know.

thanks
0
 
Darius GhassemCommented:
If you see a old DC then run metadata cleanup.

http://www.petri.co.il/delete_failed_dcs_from_ad.htm
0
 
Plaintree_SystemsAuthor Commented:
Going throught the KB it says to copy my domain folder into the same location on server2.

I noticed that the sysvol folder on server2 isn't shared. Can I manually share it to make it match server1?

thanks

0
 
Plaintree_SystemsAuthor Commented:
Didn't get the issue solved as of yet- System will have to be demoted and hopefully that will fix the issue.

Will have to wait for plant shutdown.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.