Error when trying to promote DC (the specified network name is no longer available)

Azy1412 211 Reputation points
2020-08-06T09:29:17.893+00:00 
 We just deployed a new VM in a different site to act as an RODC.

But the issue is when we try to promote to DC, we get the following error;

The wizard cannot access the list of domains in the forest. the error is:
The specified network name is no longer available .

16026-1.png

server can reach the domain controllers, but from the domain controllers' it is not reachable.
client machines are able to reach the server, but the server is not able to reach the client machines.

I've turned off the firewall on the new server, still the issue is occuring.
I've our security team and they claim that everything is clear on their end.

also, can we join servers/workstations if we only have an RODC in that site ?

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,149 questions
0 comments
Accepted answer
  1. Dave Patrick 426.4K Reputation points MVP
    2020-08-09T14:26:11.613+00:00

    Yes, it would have helped to mention the environment.

    The two prerequisites to introducing the first 2019 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
    https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.4K Reputation points MVP
    2020-08-06T12:20:29.43+00:00

    I'd check the required ports are flowing between sites.
    https://support.microsoft.com/en-us/help/179442/how-to-configure-a-firewall-for-domains-and-trusts

    https://www.microsoft.com/en-us/download/details.aspx?id=24009

    --please don't forget to Accept as answer if the reply is helpful--

  2. Vicky Wang 2,646 Reputation points
    2020-08-07T06:32:19.3+00:00

    Solution - Check the following services on the domain machine

    • Browser service
    • Workstation
    • Server

    And start them. This should solve the issue.

    Best Regards,
    Vicky

    0 comments
  3. Dave Patrick 426.4K Reputation points MVP
    2020-08-09T12:26:06.41+00:00

    I'd check the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS

    --please don't forget to Accept as answer if the reply is helpful--

  4. Vicky Wang 2,646 Reputation points
    2020-08-17T07:01:14.463+00:00

    Hi,
    I am glad to hear that your issue was successfully resolved.
    If there is anything else we can do for you, please feel free to post in the forum.
    Have a nice day!

    0 comments