Event ID 192 — AD RMS Cluster URL Availability
Applies To: Windows Server 2008 R2
Active Directory Rights Management Services (AD RMS) uses a cluster URL that all AD RMS clients use to publish and consume rights-protected content. After a successful AD RMS installation, the cluster URL is contacted to ensure its availability on the network.
|Product:||Windows Operating System|
|Source:||Active Directory Rights Management Services|
|Message:||The cluster URL specified in the Active Directory Rights Management Services (AD RMS) installation did not respond to an HTTP request. Make sure that the AD RMS cluster is available on the network.|
Create AD RMS port exceptions for Windows Firewall
AD RMS uses TCP port 80 and TCP port 443 to communicate with AD RMS-enabled clients and other AD RMS servers in the cluster. Failure to communicate with these ports could mean that the AD RMS cluster is not available on the network or the ports are restricted by a firewall. Use the following sections to establish basic network connectivity with the AD RMS server and create the appropriate port exceptions in Windows Firewall.
To perform these procedures, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.
Ensure network connectivity with the AD RMS cluster URL
To ensure network connectivity with the AD RMS cluster URL:
- Type ipconfig /all at a command prompt on the AD RMS server. Make sure that the AD RMS server has an IP address in the correct IP address range, and does not have an Automatic Private IP Addressing (APIPA) address (an IP address in the 169.254.x.x range).
- Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with the network adapter.
- Type ping ip_address, where ip_address is the IP address assigned to the computer. If you can ping the localhost address but not the local IP address, there may be an issue with the routing table or with the network adapter driver.
- Type ping dns_server, where dns_server is the IP address for the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the AD RMS server and the DNS servers.
- Type nslookup **adrms_cluster_url, where adrms_cluster_url is the name of the AD RMS cluster, and then press ENTER. If the **nslookup does not return an associated IP address for the AD RMS cluster URL, this may indicate that there is an issue with the DNS cache. To flush the DNS cache, type ipconfig /flushdns from a command prompt.
Create port exceptions in Windows Firewall for AD RMS communication
To create port exceptions in Windows Firewall for AD RMS communication:
- Click Start, and then click Control Panel.
- Double-click Windows Firewall, and then click Change Settings.
- Click the Exceptions tab.
- Select the World Wide Web Services (HTTP) check box.
- Select the Secure World Wide Web Services (HTTPS) check box.
- Click OK.
- Repeat these steps on each AD RMS server in the cluster.
To perform this procedure, you must be a member of the local Users group, or you must have been delegated the appropriate authority.
To verify that the AD RMS cluster URL is available on the network:
- On a computer in the same Active Directory forest as the AD RMS cluster, click Start, point to All Programs, and then click Internet Explorer.
- In the address bar, if the cluster is using HTTP communication, type http://adrms_cluster_url/_wmcs/certification/certfication.asmx, where adrms_cluster_url is the URL assigned to the AD RMS cluster. If the cluster is using HTTPS communication, type https://adrms_cluster_url/_wmcs/certification/certfication.asmx, where adrms_cluster_url is the URL assigned to the AD RMS cluster.
- Verify that the Web page resolves to a Web page with a title of CertificationWebService Web Service.