-
1. Re: Connector Activation problem
oivinde May 8, 2013 12:46 PM (in response to Adam Cook)I've had this issue once, but after verifying that IP-Pool in vCenter was correctly configured (used static IP's on the appliances, so stay clear of the scope in the IP-pool), and cleaned up and recreated (and verified) the DNS-records (and PTR), including configuring split DNS for the gateway-va, problem was gone.
br
Oivind
-
2. Re: Connector Activation problem
Adam Cook May 9, 2013 7:07 AM (in response to oivinde)I just double checked those, and they are all correct. The IP Pool set up correctly and the va machines are using static IPs. The PTR and DNS records are correct.
-
3. Re: Connector Activation problem
sravuri May 9, 2013 8:36 AM (in response to Adam Cook)Do you see anything relevant in configurator or connector logs?
configurator VA: /opt/vmware/horizon/configuratorinstance/logs/configurator.log
connector VA: /opt/vmware/c2/c2instance/logs/connector.log
-
-
5. Re: Connector Activation problem
sravuri May 9, 2013 9:08 AM (in response to Adam Cook)can you also include connector log?
-
6. Re: Connector Activation problem
Adam Cook May 9, 2013 9:10 AM (in response to sravuri)1 person found this helpful -
7. Re: Connector Activation problem
sravuri May 9, 2013 9:14 AM (in response to Adam Cook)Looks like the connector is not able to access the horizon.data-strategy.com. Is that the FQDN? Does the FQDN have a PTR record?
-
8. Re: Connector Activation problem
Adam Cook May 9, 2013 9:15 AM (in response to Adam Cook)It seems like the connector can not contact the gateway. I tried to ping and browse to the URL and i got nothing
-
9. Re: Connector Activation problem
Adam Cook May 9, 2013 9:17 AM (in response to sravuri)Yes it is the FQDN and it does have a PTR
-
10. Re: Connector Activation problem
Adam Cook May 16, 2013 6:15 AM (in response to Adam Cook)I ended up redeploying with totally different IP addresses and it worked. I may have had an IP conflict or something. Thanks for the help!