View 4 Client and Connection Server – incorrect connection IP address

[bhallinan]

My View client is connecting on the wrong IP address. Both the View client and the View Connection Manager have two network adaptors - one for network traffic (10.192.53.xxx) and one for iSCSI storage (192.168.0.xxx). When the View client connects, it attempts to connect via storage network.

Is there any way to reconfigure or force the PCOIP connection to the network (10.192.53.xxx)?

The PCOIP log file (pcoip_client_YYYY_MM_DD_*.txt), shows the following. Note the IP address 192.168.0.124 should be 10.192.53.224 in the log below.

CLIENT :DAConnect '192.168.0.124:50002;0089146d10e748489ce89f4808c4cb31'

CLIENT :tera_pcoip_connect '192.168.0.124:50002;0089146d10e748489ce89f4808c4cb31'

CLIENT :Session Tag found as '0089146d10e748489ce89f4808c4cb31'

CLIENT :Session Port found as '50002'

CLIENT :Session Addr found as '192.168.0.124'

CLIENT :Session Tag set to '0089146d10e748489ce89f4808c4cb31'

MGMT_SYS :Connecting with host (192.168.0.124, 00-00-00-00-00-00)

CLIENT :DASetConnectedCb called, connected = 1.

MGMT_SESS :PCoIP session type (PRI: 0)

MGMT_SSIG :Initiating session with: (192.168.0.124)

MGMT_PCOIP_DATA :Tx thread info: bw limit = 0, plateau = 0.0, avg tx = 0.0, avg rx = 0.0 (KBytes/s)

VGMAC :Stat frms: R=000000/000000/000000 T=000000/000000/000000 (A/I/O) 0.00% lost

MGMT_SSIG :Session timeout (192.168.0.124)!

MGMT_SCHAN :scnet_client_open: tera_sock_connect failed to connect to 192.168.0.124:50002!

MGMT_SCHAN :SCDAT: master_ready(): Failed scnet_client_open

COMMON :tera_sock_unregister_cback failed - socket not found!

SCNET :scnet_reset: SSL_shutdown: sv=-1, rv=1

COMMON :TERA_PCOIP: SESSION_EVENT=TERA_MGMT_SYS_SESS_EVENT_OPEN_TIMEOUT

Thank you.

[Linjo]

There is currently not a way to specify what nic PCoIP will bind to, it grabs the first one.

A workaround is to change the order in your networks to have your "client" network first in the list.

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[bhallinan]

The problem was solved to reconfigure or force the PCOIP connection to the appropriate network. It was done by configuring the connection access order to be the same, with the desired network first, for the View Target VM, View Connection Server, and vCenter Server. Using the windows Network Connections -> Advanced -> Advanced Settings -> Adapters and Bindings tab, the 10.192.53.xxx network adaptor was moved to the top of the connections list. Thank you, Linjo.