• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 53
  • Last Modified:

DNS 4000/4015 Error, ADDS 1925 Error

Hi All,

I recently had to rebuild a Windows Server 2k12R2 Server. Current Set-Up

2 x Windows Server 2k12R2

DC01 has all the FSMO roles
DC02 (before rebuilt) - kicked it off the domain, demoted the server
DC02 (rebuilt) - I gave it the same name and IP address as the one that I demoted.

Issues:
  • I'm unable to replicate, when I do repadmin /syncall, it says that the RPC server is unavailable
  • I am able to ping the rebuilt DC02 by IP
  • I have attached a screen shot of dcdiag
  • It says no host record, but when I check the DNS manager of DC01 and DC02, I do see it
0
Steven Hoong
Asked:
Steven Hoong
  • 3
  • 3
  • 2
1 Solution
 
arnoldCommented:
You forgot after demotion to cleanup the metadata.
RPC unavailable deals with RPC port being blocked.

Double check the network association, it should be in a domain environment, yours might be detected as public at which point the advanced Windows firewall rules based on public domain will not allow inbound RPC connections.


Check the network association on both DCs... To confirm...

It is. Unnecessary to use/reuse DC names. Often, without metacleanup reusing names could result. The new inheriting problems from the prior.

When you rejoined the domain did you get a notice that a record for this account already exist?
0
 
Steven HoongSystems AdministratorAuthor Commented:
Both networks state it is under our domain.

When I rejoined the domain, I don't recall getting a notice for a record that already exists.
0
 
arnoldCommented:
Check advanced firewall rules dealing with incoming connection, check for RPC and make sure it is authorized on the domain...


Check the advanced firewalls on the other DC, I.e. Run the same command repadm in /showrep and see whether both have the same error or only one.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
MaheshArchitectCommented:
what problem dc have before rebuild?

it might be possible that problem may not cured

RPC server unavailability happening because of name resolution failure

just restart net logon service on both DCS and then check
also then check if dns records such as ns, cname, host a etc are available on both dc for both
0
 
MaheshArchitectCommented:
if still problem persists, run dcdiag /v on problematic dc and post results here
0
 
Steven HoongSystems AdministratorAuthor Commented:
so something just happened now where the entire DNS tanked and our devs couldn't get to our resources in AWS. I fired up the old DNS server and everything is fine now.

Any suggestions going forward?
0
 
MaheshArchitectCommented:
this issue is different from 1st one but related to name resolution only
if u could rename dc2 hostname, it's likely to solve issue
hopefully it will start replication
0
 
Steven HoongSystems AdministratorAuthor Commented:
that's what I did with the old server i fired back up, thank you
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.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now