Devices can't connect to Mobility server (firewall, port-forwarding)

  • 7012619
  • 17-Jun-2013
  • 02-Oct-2014


Novell GroupWise Mobility Service
Novell Data Synchronizer Mobility Pack


Device shows Unable to connect to server.
Mobility connector is listening, but devices can't connect.


  1. Determine the Mobility Connector Port for incoming device connections:
    DataSync WebAdmin
    | Mobility Connector Settings | Connector Port (default secure: 443)
    Note: For a list of commonly used ports used by GroupWise, Data Synchronizer - see TID 7009520

  2. Configure the network to appropriately allow and/or forward this traffic to the Mobility server:
    Note: Often times users enter a public server address that can be accessed from internet when adding an account to their device, but, depending on network configuration, that does not necessarily mean the connection reaches the Mobility server. Typically, this connection must be allowed to pass through a firewall and then forwarded to the internal Mobility server.
    • Firewall configuration:
      A firewall intercepts all communications between you and the Internet and decides if the information is allowed to pass. Access rules are made to block or allow specific ports. It is important that the port configured for the Mobility Device Sync Agent be allowed through the firewall.
    • Port forwarding:
      Once the packet is through the firewall, it must be forwarded to the appropriate internal server. Port forwarding allows remote computers (for example, computers on the Internet) to connect to a specific computer or service within a private local-area network (LAN). Forward incoming traffic on the specified port to the internal ip address of the Mobility server.


The device's request never reaches the Mobility server. This is most likely because port forwarding is not properly configured.

Additional Information

See TID 7012815 - How to troubleshoot device connectivity with Mobility.