Remote Workstation Card TCP Port 50001 Retirement

Rate this Article
No votes yet

August 2, 2018

Last modified: 11/09/2022, 6:49 am

Knowledge Base Article Advisory Session Remote Workstation Card Zero Clients

PCoIP Zero Client to Remote Workstation Card communication that previously was done on port 50001 is now being moved to within the PCoIP data stream in the firmware release 4.5.0. This was done to accommodate antivirus software that would identify this traffic as malicious and caused network administrators issues when configuring their PCoIP networks.

Due to the retirement of port 50001, certain behaviours between PCoIP Remote Workstation host PC's and PCoIP Zero Clients will change. The tables below identify these changes.

NOTES:

Some host PC OSs shuts down or enter sleep mode too fast and the Remote Workstation Card does not get notified of the power shutdown. In such cases, the PCoIP Remote Workstation Card does not have time to notify the PCoIP Zero Client that it is powering down. Hence when the Remote Workstation Card gets powered down, the PCoIP Zero Client will think that the Remote Workstation Card has disappeared and disconnects the session (shown as session lost).

This change does not affect brokers using the Connection Management Interface (CMI).

Affected Function /Session State

Resulting behaviour when o ne PCoIP endpoint has firmware 4.5.0 or newer  applied and the other PCoIP endpoint has a firmware 4.2.0 or older applied

Remote PC power button

When the power button is pressed on the PCoIP Zero Client, the Remote Workstation host power control is sent to the host PC for a soft or hard power off.
  • Host will not power down
WOL Configuration
  • PCoIP session does not resume
    • requires host software
    • Host PC will awaken ONLY if the previous WOL configuration is still valid
Host Power LED Status
  • Host PC goes into sleep updating the PCoIP session LED
  • On Resume the host PC awakes but the  PCoIP session does not resume
SLP Discovery
  • Host Card not listed in discovered SLP devices list

Session Wakeup

(e.g. when initiating a mouse or keyboard event)
  • The remote host PC wakes and the session times out (up to a maximum of 5 minutes) with an unable to wake host message and returns to the OSD connect screen. At this point pressing the Connect button establishes a PCoIP session

 

Host Discovery

Messages sent during the process of Host discovery

The Session State polling inquiry message and Session Peer Information polling inquiry message that was communicated over port 50001 have been deprecated. These inquiries used to originate from Zero Client to Remote Workstation Card. Instead, such session related information of the Remote Workstation Card is added onto the Service Locator Protocol (SLP) record (e.g. "attr1=value1,attr2=value2,.."). The Zero Client processes the SLP record to obtain the same information.

New SLP attributes:

  • Connection State
  • Session State
  • Peer MAC address (used by the Zero Client to determine if a sleeping Host is connected to the client doing discovery)

Retired SOAP Messages on Port 50001:

  • Host's session state (tera_mgmt_cmi_call_peer_rpc_get_session_state()) - The client originates this RPC and queries the host to determine its session state so that it can be presented to the user as part of the SLP discovery process.
  • Host's session info (tera_mgmt_cmi_call_peer_rpc_get_connected_session_info ()) - The client queries the host to obtain its sleeping state and Peer MAC.

Interoperability table showing client/host behavior if one is running OLD firmware (SOAP-based), and the other NEW firmware (SLP attribute-based):

Message / Function    Client Applied Firmware Host Applied Firmware Resulting Behaviour
Session State / Info > 4.2.0 \u2264 4.2.0

Client would be expecting to receive Host's state as an attribute but would not get it. Since we can't get enough information about this Host it would not be included in the list of available Hosts presented to the User.

  • Host Card not listed in discovered SLP devices list
Session State / Info \u2264 4.2.0 > 4.2.0

Client will be able to pick up the record and find out the host's ip address. However, the subsequent peer-to-peer CMI call to the host in finding additional information such as session state will fail (host is no longer processing peer-to-peer CMI calls) hence the client will not display the host as available in the OSD dialog. MC will still be able to discover the new hard host.

  • Host Card not listed in discovered SLP devices list
  • MC can still discover the host card

 

Session Sleep/Awake Mode

The wakeup notification is moved from port 50001 to port 4172. Message format has also changed (SOAP to HTTP format) Interoperability table showing client/host behavior if one is running OLD firmware (Port 50001, SOAP message format), and the other NEW firmware (Port 4172, HTTP message format):

Message / Function    Client Applied Firmware Host Applied Firmware Resulting Behaviour
Session Wakeup > 4.2.0 \u2264 4.2.0

Client would not receive "resume session" request on port 4172 and would remain in the sleep state.

  • Host PC wakes and the session times out (up to a maximum of 5 minutes) with an unable to wake host message and returns to the OSD connect screen. At this point pressing the Connect button establishes a PCoIP session
Session Wakeup \u2264 4.2.0 > 4.2.0

Client would not receive SOAP message to wake-up and would remain in the sleep state.

  • Host PC wakes and the session times out (up to a maximum of 5 minutes) with an unable to wake host message and returns to the OSD connect screen. At this point pressing the Connect button establishes a PCoIP session

 

Pertains to:
  • Remote Workstation Card 4.0.2
  • Remote Workstation Card 4.0.3
  • Remote Workstation Card 4.1.0
  • Remote Workstation Card 4.1.1
  • Remote Workstation Card 4.1.2
  • Remote Workstation Card 4.2.0
  • Remote Workstation Card 4.5.0
  • Remote Workstation Card 4.5.1
  • Remote Workstation Card 4.6.0
  • Remote Workstation Card 4.7.0
  • Remote Workstation Card 4.7.1
  • Remote Workstation Card 4.7.2
  • Remote Workstation Card 4.7.4
  • Remote Workstation Card 4.7.5
  • Remote Workstation Card 4.9.0
  • PCoIP Zero Client 4.0.2
  • PCoIP Zero Client 4.0.3
  • PCoIP Zero Client 4.1.0
  • PCoIP Zero Client 4.1.1
  • PCoIP Zero Client 4.1.2
  • PCoIP Zero Client 4.2.0
  • PCoIP Zero Client 4.5.0
  • PCoIP Zero Client 4.5.1
  • PCoIP Zero Client 4.6.0
  • PCoIP Zero Client 4.7.0
  • PCoIP Zero Client 4.7.1
  • PCoIP Zero Client 4.8.0
  • PCoIP Zero Client 4.8.1
  • PCoIP Zero Client 4.8.2
  • PCoIP Zero Client 5.0.0
  • PCoIP Zero Client 5.0.2
  • PCoIP Zero Client 5.1.0
  • PCoIP Zero Client 5.1.1
  • PCoIP Zero Client 5.2.0
  • PCoIP Zero Client 5.2.1
  • PCoIP Zero Client 5.2.2
  • PCoIP Zero Client 5.3.0
  • PCoIP Zero Client 5.4.0
  • PCoIP Zero Client 5.4.1
  • PCoIP Zero Client 5.5.0
  • PCoIP Zero Client 5.5.1
  • PCoIP Zero Client 6.0.0