Unable to replicate

[sharyn]

All of a sudden, over the weekend, one of my win2k DC's is unable to replicate with its primary replication partner, or any of my other DC's for that matter.

I am unable to ping, from this particular server, using the FQDN of my other servers, however, I can still ping using their internet domain name, and netbios name.

The AD zone is showing as running on this box. Every other server can ping each other using FQDN. Every other server can also ping the server in trouble, using its fdqn.

My guess is that even though the AD zone shows its running, something isnt right. Anyone seen this before? Would deleting the zone on the server having problems and recreating it fix this? Uninstalling and reinstalling DNS?

This server is receiving incoming replication information, it just cant seem to push anything out, do to the inability to resolve the fqdn of its replication partners.

Suggestions and advice would be appreciated as it seems its just this one server that is having problems. Everything else, WINS, DHCP, and authentication seems to be fine.

Really weird, one last note, and this must be a coincidence but who knows? I *did* upgrade another nt 4.0 BDC this weekend in a totally different site. I don't see how this could have anything to do with anything but what do I know? The server I upgraded seems to be fine, but the server having problems seems to have acquired it's problems right around the same day/time I was doing the upgrade on the other server.

Thanks in advance!

Sharyn

 

[GlenJohnson]

Hows your dns. AD relies heavily on it. What does route print tell you from the bad server. (Maybe during the promo, you set the server to replicate with the bad server? Just a though.) Start with DNS log. (If you go to Active Directory Sites and Services, can you force replication?) Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com

"There is nothing in this world constant but inconstancy."
Jonathan Swift (1667-1745); Irish author.

 

[sharyn]

The server I upgraded is NOT the one having the problems.

DNS is working for every other server but the one I'm having problems with. All servers are using the exact same AD dns zone.

I can force a replication with every server except the one I'm having problems with. This is the ONLY server that is not able to resolve the FQDN.

I can ping everything in creation from the problem server EXCEPT for servers in my AD zone.

This stinks of a DNS issue on the problem server. Has anyone seen this before?

Bront?? Are you still monitoring this list???????

Sharyn

 

[GlenJohnson]

Have you re-booted the bad server? Did you check it for dns error messages? How about the route print? (Bronto would be the one with the awnser, I'm just giving suggestions.) Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com

"There is nothing in this world constant but inconstancy."
Jonathan Swift (1667-1745); Irish author.

 

[CoolClark]

Are you getting any Event Errors?

 

[sharyn]

No, I did not reboot the bad server. I am unable to reboot it, it is in a remote office and I won't take a chance on rebooting unless I have time to run out there in case it won't boot back up. Like I said, everything else is working.

I am getting no DNS error messages, but I am getting the KCC error message telling me it cant resolve the replication partner's name.

What is a route print?

 

[CoolClark]

Try creating a manual replication object with another DC and see if that works.

 

[sharyn]

Thanks, I tried that.

This server that I"m having problems with will not replicate at all, it has just stopped resolving the fully qualified domain name of every machine in my AD zone. That is the kcc error I get in event viewer. I can cut and paste the exact error when I get back to work tomorrow, I'm sure it will still be there !

I tried that route path thing, everything looks normal. Like I said, the server ACTS like its fine, I never wouldve known it wasnt replicating had I not checked REPL Monitor to see what the status of the newly upgraded DC was.

Very very strange!

Good idea though, thanks.

Sharyn

 

[GlenJohnson]

I've been told the KCC error's are AD errors since it can't replicate which in turn pointst to DNS. Your'e first assumpation about DNS is correct. Have you done anything different like installing SP3? Something changed to make this happen. (Checked for viruses, break ins?) Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com

"There is nothing in this world constant but inconstancy."
Jonathan Swift (1667-1745); Irish author.

 

[sharyn]

The only thing that changed over the weekend was upgrading a totally different server. This is what really doesnt make sense.

I believe I am going to try rebooting the thing today though before I recreate the zone.

Win2k DNS Gurus? Question?

If I delete the AD zone on JUST THIS SERVER, is it going to have an effect on any of the other servers running the same AD zone?

Sharyn

 

[sharyn]

Ok folks,

I feel like I'm in the twilight zone. I just logged onto my server that was giving me replication problems and it has magically fixed itself.

It is back to replicating with the server its supposed to be replicating with, this happened sometime this morning around 4am.

Just like it broke by itself, it fixed itself. I sure wish I knew what was going on. Has anyone seen anything like this before????????????????

No, I have not been Drinking!

Sharyn

 

[sharyn]

And, of course, I can now ping all my other boxes in my AD zone by fqdn.

I SWEAR I feel like Im in the twilight zone!

 

[GlenJohnson]

When you signed on, was that after a re-boot? That's the first thing I do on ALL pc's, be they servers or desktops. PC's are just machines, they forget sometimes.

Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com

"There is nothing in this world constant but inconstancy."
Jonathan Swift (1667-1745); Irish author.

 

[sharyn]

No, I never had a chance to reboot the server, I just signed on and it was magically fixed.

Thanks for everyones help!

Sharyn