Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Steve Perrins

Migrating SBS 2011 to Server 2019 Standard - Step 7.23 - Error With dcdiag /test:topology

Hi,

I have run all the commands up to 7.23 and everything appeared to go smoothly. However in step 7.23 it is advised to run dcdiag /test:topology ,  this produces the following results:

Step 7.23

PS C:\Windows\system32> dcdiag /test:topology

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = SL-DC2019
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\SL-DC2019
      Starting test: Connectivity
         The host f63338d9-d38b-4e6b-be4e-e8d6bcdbe670._msdcs.saith.local could not be resolved to an IP address. Check
         the DNS server, DHCP, server name, etc.
         Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
         ......................... SL-DC2019 failed test Connectivity
Doing primary tests

   Testing server: Default-First-Site-Name\SL-DC2019


   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : saith

   Running enterprise tests on : saith.local

 

Any clues on what's gone wrong how I can fix this.

 

Thank you

Steve.

 

asked01/15/2020 16:41
188 views
Add Comment
Mariette Knap

I would reboot both DC's and after the 2019 is back on restart the NLA service. Make sure that the Domain Firewall profile is active on your network connection. You can check that in Server Manager, Local server

Steve Perrins

Hi Mariette,

Thanks for taking the time to reply. 

Whilst I was waiting on an answer I performed the following (might be useful for others):

  1.  Edited the hosts files on the WS2019 server and added an entry to point the WS2019 IP address to the host name in the error, i.e. 192.168.20.112 f63338d9-d38b-4e6b-be4e-e8d6bcdbe670._msdcs.saith.local
  2. Re-ran dcdiag /test:topology - Result all good
  3. Moved on to Step 8 DNS, and completed
  4.  Removed entry from hosts file and retried dcdiag /test:topology - Results all good
Step 9. Active Directory Health and Replication - Results all good
 
Now waiting for the weekend to run the rest of steps.
 
Thanks again,
 
Steve

 

replied 01/15/2020 18:51
Reply
Last Activity 01/16/2020 04:28

1 Answer(s)

  • Mariette Knap

    Host files should never be used to solved DNS problems. It may work for you now but it will cause problems in the future.

    answered 01/16/2020 04:28
    Add Comment
Add an Answer