Last Reviewed 27-Jul-2005 Applies ToMobility 6.01 and earlier Printer-friendly version
Some WWAN cards require configuration on the client PC to enable them to work properly with Mobility XE 6.01 and earlier (version 6.50 and higher of the Mobility client does not require passthrough configuration for WWAN connection managers). The Mobility client tunnels all IP traffic to the Mobility server, and because some card managers try to communicate with the WWAN card via IP, their calls to the stack get redirected and the card manager doesn't function properly. The Mobility client needs to let traffic destined for the local hardware to "pass through" so that the card's software can work. This technical note describes how to identify when a problem is a passthrough issue, and how to correct it.
There are situations in which modem commands do not reach the card in a format that the card can understand. The symptoms are:
The WWAN card is not able to connect or disconnect unless Mobility is enabled.
The card may disconnect as soon as Mobility is connected.
When Mobility is in Bypass mode the card functions normally.
Your problem will likely be resolved by installing version 6.50 or higher of the Mobility client, which does not require passthrough configuration for WWAN connection managers.
If you do not want to upgrade to 6.50 you can add your connection manager to the Mobility client's passthrough list in the device's registry. There are two ways to do this:
Download the most recent passthrough list, which contains passthrough settings for all of the connection managers NetMotion Wireless is currently aware of.
If you have a connection manager that isn't in the passthrough list, manually add it yourself by creating a custom passthrough rule.
As Mobility identifies new hardware and software in need of passthrough rules we add them to a passthrough list (a simple text file). To download the latest version of the passthrough list, follow these steps:
Download the following file and put it on the Mobility client device (right-click the link and choose "Save Target As..." or "Save Link As..." to save the file locally): UpdatePassthruLists.txt (last updated July 6, 2005).
Rename the file by changing the file extension to ".reg" (UpdatePassthruLists.reg).
Double-click on the file to merge the updated registry settings into the device's registry.
Reboot the device.
Running this file puts the most current set of static and process passthroughs into the registry so that the Mobility client can read them. After rebooting the device, the connection management software should function properly, allowing you to make a connection to the carrier's network and to the Mobility server.
If you find an application that is not fixed by the current passthrough list, you may want to create your own passthrough rule for your card manager in the client's Windows registry to let modem commands be sent outside of the Mobility tunnel. Follow these steps (if this does not fix the problem, contact tech support):
Determine the name of the executable for the card manager (for example, "Wireless Manager.exe" or "CingularCCM.EXE") by looking at the properties of the shortcut used to launch it. Edit the properties of the shortcut and look at the Target field.
Using regedit on the client machine, navigate to the following location in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetMotion\Mobility Client\PassthruProcesses\
Add a new string value with a short, descriptive name whose value is the name of the executable from step one, for example:
Key name = "Cingular Manager" Key value = "CingularWC.exe"
Reboot the machine.
The new or updated card manager software should now behave normally with Mobility. If you encounter applications that require passthroughs, please notify our technical support team so that we can incorporate them into our product and support knowledgebase.
2132
EDGE and 1xEV-DO Cards not Working Properly with Mobility
9979
NetMotion Mobility Technical Notes
Please comment on this technical note.