Error:"Cannot connect to server" "Can't assign requested address"
Article ID: CTX279747
Updated On:
Description
>Unknown Error when we open a Desktop session
>Client may need to try to click icon more times before desktop successfully launched.
Related Desktop Case:79906917
Resolution
Add dns records in client for ICA connection replay host and issue solved.
Problem Cause
1: None ADC issue
Confirmed in client packets and NetScaler nstrace, there is no TCP connection founded for launch failed desktop session. Client did not try to establish any TCP connection for desktop launch failed scenario. Only successful ICA connection recorded and matched with customer’s test results.
2: Client DNS resolution failured from CDF trace in receiver.
A hostname is being given of HDX-dektop.server to connect to. The Client, however, is translating this to the ip address of 0.0.0.2. The Implication here is that this is a secured environment that has a proxy setting in place to redirect many undesired addresses to 0.0.0.2.
CDF Log:
37525,0,2020/08/05 17:51:22:57588,11944,7864,-1,HPC_ICA_ENG,SslASock_Api.c,467,SslASock_Connect(),1,Information,"SSL Relay host name:HDX-dektop.server resolved to: 10.204.182.11","" （working scenario）
130535,0,2020/08/05 17:51:33:46960,13344,13428,-1,HPC_ICA_ENG,SslASock_Api.c,467,SslASock_Connect(),1,Information,"SSL Relay host name: HDX-dektop.server resolved to: 0.0.0.2","" （NOT working scenario）
