Ericom Connect supports access from a wide variety of operating systems and devices.  Supported systems in version 9.0 include:

  • Any device with an HTML5 web browser (using the AccessNow interface)
  • Windows: 7, 8, 10 LTSB, 2008, 2008R2, 2012R2, 2016 LTSB, 2019 (using AccessNow or AccessPad)
  • Windows 10 SAC 1803, 1809 (using AccessNow or AccessPad)
  • Apple MacOS 10.11, 10.12, 10.13 Intel-based (using AccessNow or AccessPad)
  • Linux Ubuntu: 16.04 [XFCE, Unity, LDXE: openbox, GNOME: classic] and 18.04 [XFCE, LDXE: openbox, GNOME: shell] (using AccessNow or AccessPad)
  • Apple iOS (using AccessNow or AccessToGo)
  • Android (using AccessNow or AccessToGo)
  • Google Chromebook/Chromebox (using AccessNow)

There are two methods used to display an application or desktop:

  • Native client – this is an application that is native to the end-user’s operating system.A native client will support standard RDP features.
  • HTML5 interface – Applications and desktops that are launched will appear inside the web browser and will not require anything to be downloaded onto the end-user’s device.Features, such as printing and file transfer, are browser based and operate differently than a native RDP client.

End users may use any one of these portals to sign in and view their assigned applications and desktops:

  • AccessPortal – Web based interface that launches published applications and desktops that will use the AccessNow HTML5 protocol.The AccessNow protocol communicates over port 8080.
  • AccessPad – Native application that launches published applications and desktops that will use either the RDP or Blaze protocol.When the Blaze protocol is used - the communication is over port 8080.When the RDP protocol is used - the communication is over port 3389.
  • AccessToGo / Ericom Connect Mobile Client – Native mobile client for iOS and Android that launches published applications and desktops. Native mobile client for iOS and Android that launches published applications and desktops. Please refer to AccessToGo Manual for full details and supported operating system versions.

All three access methods are described in an easy to customize introduction page using this URL:https://<euws-server-address>:8011/ or


Starting in 8.4, there is a configurable portal timeout setting.  If a portal client (AccessPad, AccessPortal, or AccessToGo) ​has had no active RDP sessions for a period of time and detects no attempts to launch a session for a period of time, the session is automatically logged off as 'idle'.

  • To configure the timeout: there is a System level configuration setting: EndUserSessionIdleTimeoutSec which defaults to 0.  0 means that there is no idle session timeout.
  • If, there has been no active session for the EndUserSessionIdleTimeoutSec ​and no attempt to launch a session for the timeout - the end user session is classified as idle and the portal will return an error "Your session has expired… " if the user tries to launch a session (note that the client is not logged out).
  • The EndUserSession report shows “Idle Timeout" as the reason for portal session termination.

Note that "User Sessions" refer to the sessions in the Ericom portals (e.g. AccessPortal). If these are disconnected unexpectedly, a message of "lost contact" will be logged.

Remote Sessions are the RDP sessions. There is no "lost contact" status for an RDP session. Users may disconnect an RDP session from one "user session" and then reconnect from another. If the system is configured to "logoff disconnected sessions", the remote RDP session would simply be logged off.