View Replica Connection Server not listed in View Administrator Console

[MayurPatel]

I have setup a View lab environment with 2 View Connection servers CS1 and CS2 (replica). I am using v5.1.2 VMware-viewconnectionserver-x86_64-5.1.2-928164 for the installation.

After the installation and reboot of both servers I do not see CS2 listed under the connection servers, only CS1 appears in the list. However, when I connect to the View Administrator console on CS2 replica server I see both the servers in the list.
On checking the registry settings on both the servers I find the entries to be correct under HKEY_LM\Software\VMware, Inc.\VMware VDM\ServerInstanceType=1 on CS1 and =2 on CS2. I chose to set the Windows Firewall rules to Automatically update during the installation process.Both servers are on the same VLAN.

I am able to connect to the virtual desktop when connecting using the View client independently to either of the connection servers, but after doing some further testing I found the pairing is not working properly. I disabled CS1 from its own console and refreshed the servers on CS2 console and CS1 still shows as enabled after several refreshes. I also tested it from CS2 console, I disabled CS1 but it does not reflect this change on CS1 server console.

What I gather is the grouping and its pairing is not working the settings for some reason. I have tried 3-4 times the installs on vanilla Windows 2008R2 installs and each time I am getting the same results. I am wondering if anyone else has come across similar problem.

[mougT]

Make sure ADAM is replicated successfully between the servers, and that no firewall is blocking the necessary ports. You can check replication with "repadmin /showrepl localhost:389 DC=vdi,DC=vmware,DC=int"

[MayurPatel]

I have tried the repadmin /showrepl localhost:389 DC=vdi,DC=vmware,DC=int command you suggested along with a couple of others but to no avail. Even rebuilt the VMs several times after deleting the machine account in my LAB AD but continue to have the same issues. I have tried both my scripted installs as well as manual installs and each time I have encountered the same problem. This time i took some screen shots of my results in the hope to find out if others have come across similar issues. The only two things left to be eliminated in my lab environment is my AD domain controller and the fact that my Windows 2008R2 Connection server builds are from a custom Windows 2008R2 SP1 ISO which I had updated with all the hotfixes back in July 2013. - This was my next step to update each VM with the latest patches from MS.

I have even tried to revive the replication using the below commands but this doesn't seem to do anything.

repadmin /options SERVER_FQDN -DISABLE_OUTBOUND_REPL

repadmin /options SERVER_FQDN -DISABLE_INBOUND_REPL

This is the result few minutes after the installing CS1 the first connection server.

This is the output from the replica server installation CS2 5 mins after the installation completed.

The above successful replication indicates the firewall settings are allowing the replication traffic
and synchronization is working one way at this point. CS2 ---> CS1

This now the output from the first server CS1 after running the command on CS as above.
Immediately it begins to fail complaining that RPC handles are exhausted and throwing up
errors about KCC which I think are related to Kerberos??

[MayurPatel · Accepted solution]

The Problem was caused because the DNS server did not have the correct entries of the second CS server for both forward and reverse name resolution. (I had changed the IP address)