VMware Horizon Community
josefdi
Contributor
Contributor
Jump to solution

Access Point 2.8 - Horizon Client: Error Couldnt resolve hostname

Hi Guys

I get the below error when accessing externally ie from internet. Environment consist of access points, VIDM and Horizon servers. I am able to access and login to the VIDM portal and see the icons, but get the error when trying to launch the application.

VMware Horizon Client: Error couldnt resolve hostname

I am not getting any error when accesssed through internal networks to the same VIDM portal.

The connection server gateway settings are ticked (enabled) currently, if i untick them my internal connection breaks and i get error 404 error.

Are there any thoughts ?

Reply
0 Kudos
1 Solution

Accepted Solutions
markbenson
VMware Employee
VMware Employee
Jump to solution

josefdi Thanks for the .ini file. It helps.

Looks like the configuration is not quite correct.

In the [Horizon] section, you have

proxyDestinationUrl=https://connectionsvr1.domain.com

I'm assuming connectionsvr1.domain.com can be resolved by Access Point and resolves to a Horizon Connection Server in the internal network. If so, that is correct. However, the external URLs specified below this are not correct. The first two reference the same connectionsvr1.domain.com, and that is likely to be the problem here. You have:

####################################

#

# The following external URLs are used by Horizon Clients to establish tunnel, HTML Access and PCoIP connections

# to this Access Point appliance. If they reference a load balancer name or address then the load balancer must be

# configured for source IP hash affinity otherwise the connections may route to the wrong Access Point appliance.

#

tunnelExternalUrl=https://connectionsvr1.domain.com:443

blastExternalUrl=https://connectionsvr1.domain.com:443

#

# pcoipExternalUrl must contain an IPv4 address (not a DNS name)

#

pcoipExternalUrl=10.179.134.11:4172

####################################

External URLs are used by  Horizon clients, and connectionsvr1.domain.com that you have specified will probably not be able to be resolved by the client. e.g. with a Windows Horizon client you will probably see a message "Error: Unable to resolve server address. No such host known.". That happens because the client on the Internet is trying to establish a tunnel connection to connectionsvr1.domain.com and it needs to get to Access Point for this.

If this is the case, change tunnelExternalUrl and blastExternalUrl to use a hostname that the client can use to connect to Access Point. This is usually the same hostname that the client initially specifies to connect. pcoipExternalUrl is similar except that it must use an IP address. This is normally the IP address that the other ExternalUrl hostnames resolve to. It is also used by the client to connect PCoIP to Access Point.

There may be other config errors, but fix these 3 externalURL settings first and then just rerun apdeploy.ps1 command to redeploy. Retest first with a Horizon Client to make sure the Horizon settings have been corrected. If there is an error, let us know precisely what the error says, and at what stage it is shown.

View solution in original post

Reply
0 Kudos
7 Replies
markbenson
VMware Employee
VMware Employee
Jump to solution

If you launch a Horizon Client and connect to Access Point without first going via vIDM, does that work? This may not be an Access Point configuration issue. It could be the vIDM configuration.

Reply
0 Kudos
josefdi
Contributor
Contributor
Jump to solution

i assume .. to do that i need to reconfigure the access point to point to connection server & remove the reverse proxy.. I will do that and update. In the mean time, could you please tell me if the default https and blast gateway settings should be ticked or unticked in the connection server settings..Thanks.

Reply
0 Kudos
markbenson
VMware Employee
VMware Employee
Jump to solution

No. UAG can do both Horizon and Web Reverse Proxy. You need to keep both to use UAG for both purposes.

Blast gateway should be unticked on Connection Server.

If you want, attach your PowerShell .ini file and we can help further. See Using PowerShell to Deploy VMware Unified Access Gateway (formerly known as Access Point)

In the .ini file, you have both the [Horizon] section and the [WebReverseProxy] sections.

Reply
0 Kudos
josefdi
Contributor
Contributor
Jump to solution

Hi Mark...I followed the instructions having both the horizon and web proxy sections included.still getting the error

1. Internally i am able to connect to the vIDM portal - https://view.domain.com

2.Able to to launch apps and desktops. No issues

Externally , connections goes through the AP and vIDM, see attached the ini file

1. Able to connect to portal https://view.domain.com

2. Apps are listed, but getting the error - Horizon Client: Couldnt resolve hostaname. Tried changing the view client URL to IP address of the connection server in vIDM network range , this time the connection timoes out when launching the application.

\Tks

Reply
0 Kudos
markbenson
VMware Employee
VMware Employee
Jump to solution

josefdi Thanks for the .ini file. It helps.

Looks like the configuration is not quite correct.

In the [Horizon] section, you have

proxyDestinationUrl=https://connectionsvr1.domain.com

I'm assuming connectionsvr1.domain.com can be resolved by Access Point and resolves to a Horizon Connection Server in the internal network. If so, that is correct. However, the external URLs specified below this are not correct. The first two reference the same connectionsvr1.domain.com, and that is likely to be the problem here. You have:

####################################

#

# The following external URLs are used by Horizon Clients to establish tunnel, HTML Access and PCoIP connections

# to this Access Point appliance. If they reference a load balancer name or address then the load balancer must be

# configured for source IP hash affinity otherwise the connections may route to the wrong Access Point appliance.

#

tunnelExternalUrl=https://connectionsvr1.domain.com:443

blastExternalUrl=https://connectionsvr1.domain.com:443

#

# pcoipExternalUrl must contain an IPv4 address (not a DNS name)

#

pcoipExternalUrl=10.179.134.11:4172

####################################

External URLs are used by  Horizon clients, and connectionsvr1.domain.com that you have specified will probably not be able to be resolved by the client. e.g. with a Windows Horizon client you will probably see a message "Error: Unable to resolve server address. No such host known.". That happens because the client on the Internet is trying to establish a tunnel connection to connectionsvr1.domain.com and it needs to get to Access Point for this.

If this is the case, change tunnelExternalUrl and blastExternalUrl to use a hostname that the client can use to connect to Access Point. This is usually the same hostname that the client initially specifies to connect. pcoipExternalUrl is similar except that it must use an IP address. This is normally the IP address that the other ExternalUrl hostnames resolve to. It is also used by the client to connect PCoIP to Access Point.

There may be other config errors, but fix these 3 externalURL settings first and then just rerun apdeploy.ps1 command to redeploy. Retest first with a Horizon Client to make sure the Horizon settings have been corrected. If there is an error, let us know precisely what the error says, and at what stage it is shown.

Reply
0 Kudos
josefdi
Contributor
Contributor
Jump to solution

Thanks Mark. It works after i changed the external URL's to point to the access point as you mentioned.

I have specified  my internal network range as 10.0.0.1 - 10.255.255.254 in VIDM & pointed to the view server fqdn as client URL. My external setting works if point to the access point as client URL, but how i specify the external IP range ie all the IP range except 10.0.0.1 - 10.255.255.254,

Thanks again for your help.!!

Reply
0 Kudos
markbenson
VMware Employee
VMware Employee
Jump to solution

Glad you have UAG configured and working properly. That last question sounds like a vIDM question.

Reply
0 Kudos