vWorkspace not working with IPv6

Hello Mohit,

We are aware of a few issues that can be encountered when IPv6 is enabled on the vWorkspace servers. IPv6 has been seen to cause issues with licensing and the clients ability to connect to published applications. At this time we recommend that IPv6 is disabled on any servers where vWorkspace is installed, also check to make sure that you DNS servers are not providing IPv6 addresses for look ups.

IPv6 support will be included in a future release.

Regards

David

Thanks for this information David but as i had mentioned this environment is setup in client environment where we are limited only to our environment. i do not have control on cleint`s DNS server and i am sure it will cater IPv6 lookups , is there any way i can make this POC success in presence of IPv6

another query, as you told to get IPv6 disabled on all Vworkspace installed servers, does it includes VDI workstations in Computer group? because i had disabled IPv6 from all vworkspace installed servers but still sometime connection request to VDI went throught and sometime it doesnt.

Regards,

Mohit

Hi Mohit,

You would want to disable IPv6 on both the servers and the VDI's, so that if you ping the host name it does not respond using an IPv6 address.

Are your connection issues only when launching a connection to the VDI or do you have problems in authenticating to the broker for the list of published applications?

Regards

David

Hello David,

Sorry for delay reply. i am facing issues only when i launch connection to VDI, it log me off after giving error of license counts has exceeded but actually i had not yet utilized any of the license. so what i understood with this that while launching connection (as quest support explain me same) VDI session is unable to contact licensing server.

But i am surprised as i had disabled IPv6 with following command

netsh int isa set state disabled

As i saw ISATAP enabled, still it dint helped.

Now i had created a registry key under HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters

Creating DWORD 'DisabledComponents = 20(hexadecimal)'

Hope this might help.

But still i am very curious to know that when all products are supporting IPv6, Quest vWorkspace is not supporting IPv6

i think this is something quest must consider and bring a compatible version on vWorkspace soon.

Thanks ,

Mohit Goyal

Hello Mohit,

Thank you for your reply, since you are seeing errors regarding license count being exceeded I think it would be helpful for me to see this first hand. Can you open a support case so that we can discuss further and schedule a webex session to take a look at the environment?

We do have IPv6 support on the roadmap and it will be included in a future release.

Best Regards

David