Oct 19 2023 06:58 AM
Oct 19 2023 06:58 AM
We are getting this error while trying to add a directory in out multi-forest setup. The Yellow DC is advertising correctly and all ports connectivity is established with the remote forest. Please help.
Proceeding to validate that at least one of the domains associated to the obtained Forest FQDN are reachable
by attempting to retrieve DomainGuid and DomainDistinguishedName
Attempting to retrieve ForestFQDN...
Exception calling "GetForest" with "1" argument(s): "The specified forest does not exist or cannot be contacted."
There are 0 reachable domain(s) and 0 unreachable domain(s)
There are no reachable domains.
Oct 19 2023 07:18 AM
Based on the information you have provided, the most likely cause of the "GetForest" error is a network connectivity issue between the AD Connect server and the remote forest.
To resolve this issue, you can try the following:
nslookup <remote forest FQDN>
If the command returns the IP address of the remote forest, then the DNS resolution is working correctly. If the command fails, then you need to troubleshoot the DNS issue.
ping <remote forest FQDN>
If the command returns a reply from the remote forest, then the network connectivity is working correctly. If the command fails, then you need to troubleshoot the network connectivity issue.
Make sure that there is no firewall blocking communication between the AD Connect server and the remote forest. You can check this by disabling the firewall on the AD Connect server and then trying to add the remote forest to AD Connect. If you are able to add the remote forest to AD Connect with the firewall disabled, then you need to configure the firewall to allow communication between the AD Connect server and the remote forest.
If you are using a VPN to connect to the remote forest, make sure that the VPN connection is working properly. You can check this by trying to connect to other resources on the remote network over the VPN. If you are unable to connect to other resources on the remote network, then you need to troubleshoot the VPN connection.
If you have tried all of the above and you are still unable to resolve the error, then you can try the following:
Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.
If the post was useful in other ways, please consider giving it Like.
Oct 19 2023 07:49 AM
@LeonPavesic thanks for responding.
All connectivity tests on test-NetConnection, NSLookup and Ping are OK.
The Confirm-ValidDomains & Confirm-FunctionalLeve are failing.
Oct 20 2023 02:36 AM