Re: Horizon View Client 2.2 can't resolve short ho...

cahaynes86 · ‎12-11-2013

Not sure if this worked in previous versions, but the Horizon View Client 2.2 version does not seem to be able to resolve short hostnames for the Connection Server. The FQDN or IP address works fine though. Here's my config:

VMware vCenter 5.1. U1 (Build 1064983)

VMware ESXi 5.1 U1 (Build 1065491)

VMware View 5.3.0 build-1427931 (1 Connection Server)

(currently not using composer)

The View & vCenter servers are VMs running on Windows Server 2008 R2 Ent. SP1 64-bit

My laptop is running Windows 7 Ent. SP1 64-bit (6.1.7601) and I am running View Client 2.2.0 build-1404668.

DNS appears to be working fine on my desktop and all of the above VMware servers. I can perform an nslookup of the View Connection Server short hostname from the cmd prompt. The domain is defined and in the search suffix list on each device and short hostname appear to work in all other apps on my desktop. Not experiencing any DNS issues with any other applications. Even the vSphere client accepts a short hostname for the vCenter server. I know I can just use the FQDN or IP address, but I'm just curious what is preventing the short hostname from working in the View client and can it be fixed?

- Chris

Hookman · ‎12-15-2013

Chris,

Have you found a resolution to this problem?

I just upgrade a client to View 5.3, everything was working correctly until they installed the new View Client 2.2 onto their client desktops. All these client workstations are on the local internal network.

Problem is when adding the Connection server by short name they receive an error message: "network error occurred".

We are able to connect via IP and FQDN.

The local machine can resolve IP address forward and reverse to the connection server(s). We have created a workaround using a GPO to point all clients to the FQDN, but am more interested on why the new client will not work with the short name.

Jerry

cahaynes86 · ‎12-16-2013

No resolution. I just changed all the clients to start using the FQDN instead. Sounds like a bug or "new feature" added in v2.2 then. Thanks for verifying that it worked in 5.3. I will probably open a ticket with VMware when I get a chance. Just not a high priority right now.

Chris

Linjo · ‎12-16-2013

Can you ping the shortname?

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".

cahaynes86 · ‎12-16-2013

Yes. Ping works fine with the short name. Doesn't appear to be a DNS or local host issue with the short name anywhere other than in the View client itself. I can use the shortname to RDP to the Connection Server. The short name of the vCenter server works in the vSphere client on the same host too, and it's in the same domain, so even other VMware client software works with short host names ok. I can reproduce the issue on any host too. Just seems like a bug with the View client software only.

- Chris

ofox · ‎12-17-2013

We've repro it in house and are investigating the issue. Thanks for reporting it to us!

cahaynes86 · ‎12-18-2013

Great! Thanks for the update.

- Chris

admin · ‎12-26-2013

Hi cahaynes86,

We had found the root cause of this problem. We will be working on it and get back to you as soon as I have some firm update. Thank you very much!

admin · ‎12-26-2013

There are 3 Workarounds that can resolved your problem:

1. Add Environment Variables "LOCALDOMAIN" =“yourdomainname”

2. Modify the \HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Hostname from [yourhostname] to [yourhostname.domainname]

3. Add the shortname with IP to hosts files

And you can choose one of the three to resolve your problem.

Hope it useful. Thanks.

FelixYan · ‎12-27-2013

Yes, the issue have been identified internal. View Client used a 3rd party library and it has the limitation which results in this issue. Till now, we are not sure the fix will be involved in which release. But we are tracking the problem well and get back to you as soon as we have some firm update.

Thanks,

Felix

View solution in original post

cahaynes86 · ‎12-31-2013

Thank you for the update.

- Chris

FelixYan · ‎04-16-2014

Hi Chris,

We have fixed the issue. Will update you later once we have a release version.

Thanks,
Felix

cahaynes86 · ‎04-16-2014

Thank you Felix.

- Chris

Horizon View Client 2.2 can't resolve short hostname for Connection Server