Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.0 » SQL Anywhere Server - Database Administration » Starting and connecting to your database » SQL Anywhere for Windows Mobile


Creating proxy ports for Windows Mobile devices

To connect to a database server on a Windows Mobile device from the desktop, you might be required to configure a proxy port for Windows Mobile Device Center (ActiveSync) so that requests to the localhost ( IP address are passed on to the database running on the Windows Mobile device.

 To add a proxy port for a Windows Mobile device (Interactive SQL)
  1. Start Interactive SQL on your desktop computer. For the 32-bit version of Windows Mobile Device Center (ActiveSync), you must start the 32-bit version of Interactive SQL.

  2. At the bottom of the Connect window, click Tools and then choose Setup Windows Mobile Proxy Port.

  3. Click New.

  4. In the Name field, type SQL Anywhere.

  5. In the Port field, type 2639.

    This is the recommended TCP/IP port to use for a SQL Anywhere database server running on Windows Mobile. You may use other ports as long as you ensure that the database server on the Windows Mobile device is configured to use the same port.


    Every time your Windows Mobile device is cradled, Windows Mobile Device Center (ActiveSync) forwards traffic on port 2639 to the device. If you start a database server on your desktop computer while your Windows Mobile device is cradled, it cannot use port 2639. If this is problematic, you can choose another port to dedicate to Windows Mobile traffic.

  6. Click OK.

    When setting up or changing a proxy port, it may be necessary to log off and then log in to your Windows desktop in order for the new proxy port setting to take effect.

You can also configure a proxy port by setting the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services\ProxyPorts. Name the DWORD value SQL Anywhere and specify the port dedicated to Windows Mobile traffic (2639 is a good choice). Note that for 64-bit versions of Windows running a 32-bit version of Windows Mobile Device Center (ActiveSync), this registry entry will be in the 32-bit hive.


Modifying the registry is dangerous. Modify the registry at your own risk.