Unable to connect one device to the Mobility server

Some devices unable to connect to the Mobility server.
Unable to connect to Mobility server using the DNS address or ip address of the server when connected to WiFi.

Unable to connect to Mobility server with both WiFi and 3G or 4G enabled.

Other devices are able to connect using the DNS address from outside the network.

Verify the information is added correctly on the device:

1. If the server is using a self-signed certificate, please verify that Accept all SSL certificates is checked.
2. Otherwise, provide the correct information for the account and the server.
   
   

Verify the network can properly route requests to the server:

1. Disable WiFi on the device and rely strictly on 3G or 4G, or try using only WiFi instead of 3G or 4G.
   
2. Try adding the account again to the device. If connection works properly, the network needs to be properly configured to route requests (external and/or internal) to the server.
   
   

Verify the server's certificate:

1. From any web-browser visit: http://www.digicert.com/help
2. Provide the server address that is entered on the device.
3. If the Common Name is not equal to the server address entered on the device, this can sometimes cause problems. Please follow TID 7007674 to properly configure a new certificate.
   

With both WiFi and 3G or 4G enabled, the device relies on WiFi for DNS resolution. DNS address and public ip address of the server are improperly routed internally and cannot be resolved, therefore the device is unable to connect.

See TID 7012815 - How to monitor a specific device for connectivity.
See TID 7012619 - Devices can't connect to Mobility server.