Steven Hoong
asked on
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 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
ASKER
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.
When I rejoined the domain, I don't recall getting a notice for a record that already exists.
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.
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.
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
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
if still problem persists, run dcdiag /v on problematic dc and post results here
ASKER
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?
Any suggestions going forward?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
that's what I did with the old server i fired back up, thank you
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?