Cannot Connect to Windows NT Using Windows CE ServicesLast reviewed: March 18, 1998Article ID: Q176047 |
The information in this article applies to:
SYMPTOMSWhen you use Microsoft Windows CE Services (or Microsoft H/PC Explorer for Windows CE version 1.0) in Windows NT, you may not be able to connect to a Handheld PC (H/PC). You may receive one of the following error messages on the H/PC:
Remote Service not started Critical Services cannot be startedYou may also receive the following error message on the desktop computer running Windows NT:
Remote Service Start failed CAUSEThis behavior can occur if the Transport Control Protocol/Internet Protocol (TCP/IP) address of the H/PC is not in the Local Address Table (LAT) of the WinSock Proxy server.
RESOLUTIONTo resolve this behavior, use the following steps:
MORE INFORMATIONThe H/PC Explorer communicates with the HPC through TCP. The H/PC Explorer installation procedure installs the Microsoft Windows NT RAS Server for using the serial ports and assigns it to the static IP address range 192.168.55.100 to 192.168.55.102. When the HPC gets docked it dials into the Windows NT RAS Server and gets assigned the IP address 192.168.55.101. Thereafter the HPC establishes a TCP connection to the H/PC Explorer for logon. The H/PC Explorer then establishes a TCP connection to the HPC to do the actual data transfer. When the WinSock Proxy Client is installed and the IP address range 192.168.55.100 to 192.168.55.102 is not specified in the LAT, the H/PC Explorer cannot establish the connection back to the HPC. Instead it sets up a control channel connection to the WinSock Proxy server and tries to reach the HPC on the Proxy Servers external network. This is how the WinSock Proxy works by design. To let the H/PC Explorer communicate with the HPC through the local RAS server just add the IP address range 192.168.55.100 to 192.168.55.102 to the LAT.
|
Additional query words: handheld wince
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |