Debugging Hybrid Web Container Connection Issues

List of things to check if the Hybrid Web Container is not connecting to Unwired Server.

Check the Hybrid Web Container connection settings configuration on the device

  • Verify that there is a valid Unwired Server name in the configuration.

    If the Unwired Server name has changed, you must uninstall and reinstall the Hybrid Web Container on the device.

  • Verify that the configuration has a port on which Unwired Server is configured to listen for messages. The default port is 5001 but may be set differently by the administrator.
  • Verify that the port is listening. Check with the Unwired Server administrator.
  • Verify that the user name is in the configuration. If not, enter the user name in the configuration.
  • When connecting to Relay Server, verify that the connection ID (CID) is appended to the URL suffix, for example, /rs/client/rs_client.dll/<CID>/tm.

Is the Unwired Server name DNS resolvable?

Try the Unwired Server name first. If that does not work, the DNS may not be resolvable, Try the IP address instead..

Is the Unwired Server name reachable through the Internet Control Message Protocol (ICMP)?

If you cannot ping your Unwired Server name, make sure that you are on the proper network and that your VPN is established and verified as working properly.

Are Hybrid Web Container ports to Unwired Server going through the firewall?

Check to see whether the specific ports used by Hybrid Web Container to Unwired Server are going through firewalls. In a Web browser, enter http://servername:port/tm (the default port is 5001) to verify the messaging server is listening on the specified port.

.

Can an HTTP connection be established?

If the Hybrid Web Container attempted to connect to the Unwired Server and failed, verify that the HTTP connection is working by going to a website on your device's browser application.

Check settings in Sybase Control Center