Jump to content

Halo12

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Halo12

  1. When we first noticed the issues replication was failing between the 2 DCs on site, but after running the klist purge command when doing the netdom /resetpwd process there were no longer any errors. Is our situation beyond help do you think?
  2. Hello there. Yes I'm able to ping both DCs and all DCs are in the DNS zone as name servers. Each site has 2 DCs with DNS installed on it. The primary DNS is set to the other server with the secondary DNS server set to itself.
  3. Hello everyone. I'm hoping I've come to the right place. We are having AD replication errors to one of our locations (replication from this location appears to be working). There is a long line of errors (4013, 4000, 1925, 2054, 1311, 1865, 1566 - event viewer IDs). I'm trying to wade through each one but unfortunately I don't know how to implement a fix. Some key points: When running repadmin /showrepl it tells me that it cannot replicate via RPC to our other site because the remote site is unavailable. Firewall access isn't blocking any of the needed ports and I can see that our firewall is passing the traffic through Running dcdiag shows up errors about the target principle name being incorrect When I run net view using the other server's name it errors out but when I do it via IP it works When I try to manually replicate I get an error that says the naming context is in the process of being removed or is not being replicated from the specified server Looking in the _msdcs folder on the DNS console I saw that the NS was listed as an old DC that hasn't been connected for over 2 years. I have removed that entry and added our current domain controllers to it in the hope that it might help I can't even add a new DC at the site because it errored out: 'This wizard cannot access the list of domains in the forest. The specified network name is no longer available' Then there are errors around Kerberos. A commonly suggested fix of running the netdom /resetpwd command doesn't work when I try the FQDN of the server (specified network name is no longer available) but the command works when I use its IP. However, Kerberos errors are still there. I'm completely at a loss of what the cause of this (and fix) is. If anybody here has an idea of what might be happening then I'd be incredibly grateful.
×
×
  • Create New...