-
标题
Cannot open AAC "Critical error: Unable to establish a connection. No such host is known' -
说明
After installing or upgrading Active Administrator, the user installs the Active Administrator Console (AAC) on another supported computer on the network. When opening AAC, the error below is displayed:
"Critical Error: Unable to establish a connection with the server. No such host is known" when installing the Active Administrator Console (AAC).
-
原因
- Domain firewalls are enabled
- IPv6 is enabled as a dominant network protocol on the server where the Active Administrator Server Manager was installed
- The DNS PTR record does not exist and NetBIOS is disabled on the AA Console computer
-
解决办法
- Disable Domain firewalls in the Windows Firewall control panel. If this is not possible, open Control Panel | "Network and Sharing Center" | "Change advanced sharing setting" and "Turn on network discovery" and also "Turn on file and printer sharing".
An alternative to turning off domain firewall policy would be to add the following rules:
2. Disable IPv6 on the server where Active Administrator is installed.
Unchecking the IPv6 option in the adapter properties, this does NOT disable IPv6.It is necessary to “clear”, “reset” and disable IPv6 on the Active Administrator server:* Disable IPv6 - http://support.microsoft.com/kb/929852Use the “Disable IPv6”On some operating systems there is a “Fix it” from Microsoft* After installing Active Administrator Console, reboot the server* Open DNS. Delete all records for for the Active Admiinistrator serverThere should be at least two records. One for IPv4 and one for IPv6* Log into the Active Administrator server as a Local AdministratorFrom CMD window: "ipconfig /flushdns"(Clear DNS resolver cache)Then run "ipconfig /registerdns"(Re-register DNS with servers)* Reboot Active Administrator server* Ping the Active Administrator server to verify the IPv6 setting does not respond.On any machine where the Active Administrator Console (AAC) will be installed, it will be necessary to reboot the system or manually flush the resolver cache as in the above steps.
3. Click Here for Solution Article 149943 regarding resolution.
If the console will still not connect, please try adding the FQDN, shortname and IP address of the AA server to the hosts file of the remote machine where the console is installed.