The Mobility Client Connect window displays
information which can be used to determine why a connection attempt might
not be succeeding.
No local IP interface
When the status bar indicates Opening Connection
and the packet counts stay at
0, then most likely the system doesn't have Internet connectivity. In
this case, open the Windows Network Connection utility, by clicking Start
> Programs > Accessories > Communications > Network Connections,
and check the status of the LAN or wireless connections. If none
of the connections have a status of Connected (that is, there are no connections
defined, or those defined have a status of Not Connected or Disabled),
then an Internet connection has not been established.
Out of range/Firewall/Connection Manager down
When the status bar transitions from Opening Connection
UDP to Trying
HTTP before failing, then the
Mobility Client has a valid IP interface to use, but that interface is
failing to contact the Connection Manager. This problem could occur for
device could be out-of-range and data is not reaching the Connection Manager.
personal firewall installed on the system might not be correctly configured
to allow artcore.exe to send and receive data.
physical firewall in the path is discarding data.
Connection Manager is not running.
Connection Manager system is not connected to the Internet.
Mobility Client is configured with the wrong address or port for the Connection
The status bar also lists the name of the interface being used.
A suggested action to take towards resolution would be if browser access
is available, preconfigure the browser with two favorite hyperlinks to
test the connection to the Connection Manager. For example, one for
the East, one for the West.
The format would be:
If this page is not successfully rendered, then the system does not have
network connectivity to the Connection Manager.
GINA connection failures
If GINA fails to establish a connection, users might need to log in with
cached Windows credentials before problem determination can be attempted.
If the Mobility Client is unable to establish contact with the Connection
Manager, the login does not proceed past the point in which it is looking
for network and making initial contact. This problem includes the
situation where a user is first required to use a browser to accept conditions
prior to using a given network. Users might need to log in with cached
Windows credentials to understand why they are unable to establish a connection.