Reason 2: "Terminated by Mobility Server"
Technical Note 1487
Last Reviewed 11-Jul-2005
Applies To
Mobility client, version 6.01 and lower
Printer-friendly version
Summary
This technical note provides information for troubleshooting random disconnections from the Mobility server. This is typically caused by duplicate permanent identification numbers (PIDs) in Mobility generated by disk-cloning products.
In version 6.50 of Mobility XE device hardware signatures prevent duplicate PID problems—upgrade to version 6.50 to avoid this problem altogether.
About the Permanent Identification Number (PID)
The first time a Mobility client connects to a Mobility server, the server registers the mobile device and assigns it a unique permanent identification number (PID), which the client uses for all subsequent connections. This identification number is stored in the client system registry.
The PID number must be unique because duplicate PIDs cause sessions to disconnect.
Disconnection Error Messages
If multiple mobile devices have the same PID, each device is able to connect to the Mobility server. However, when the second device connects, the first device is disconnected.
When the second device connects, the Mobility taskbar icon on the first device turns red and the user receives a disconnect error.
The Mobility event viewer on the disconnected Mobility client mobile device displays the following message:
Network Circuit indicated a disconnect, how: Abort, reason: Terminated by Mobility Server.
The Mobility event viewer on the Mobility server displays the following message:
Info 6/2/00 14:06:20.907 Proxy NetMotion Client TDI RPC disconnect indication, virtual address: 111.222.44.55, IMP handle: 0x06bcfd4c, how: Abort, reason: Terminated by Mobility Server.
The IP address indicated in the above error refers to the virtual IP address, which is reassigned from the first device to the second.
Note: This error is an indication of the presence of duplicate PIDs, but may also occur in other circumstances.
Deleting the PID Number from the Windows Registry
If multiple devices have the same PID number, edit the Windows Registry and delete the PID number on all devices. A new PID number will automatically be assigned the next time the mobile devices connect to the Mobility server.
Please see Technical Note 1486 for instructions to delete the PID value from the registry.
Related Information
1486
|
Reason 69: "The Client Session No Longer Exists"
|
9979
|
NetMotion Mobility Technical Notes
|
Please comment on this technical note.
