Yet Another Palm Site

Connecting a Palm Pilot to Windows 2000


As with the FreeBSD info, this document contains instructions on how to connect a Palm Pilot to a Windows 2000 machine for Dial-in style connectivity. (All work was carried out on Windows 2000 Server (build 2195) - I presume the RAS setup will be similar on Win2k Professional). Note this doc is a bit heavy with images. This document is available with with or without inline images.

Making the Connection


  • Windows 2000 (Server)
  • Palm Pilot (Successful reports for: IIIc, IIIe, V, Vx, m100, m500 (non USB), m505 (non USB), Unsuccessful: None, No report: m105, VII, VIIx)
  • Link Direct (Not required for PalmOS 3.3 and greater)
  • Networking

Windows Setup

  • Navigate to the Phone and Modem options section in the Control Panel
  • From the Phone and Modem Options, install a null modem (Comms Cable between two computers) cable connection. If this is your first attempt at this, Windows will probably whinge to setup the area codes. For the baud rate, set it at 19,200 for debugging attempts. If and when you get it working, you can jack the connection rate up to 56,700bps (If you're using Link Direct of course). Corrado De Sanctis has pointed out that you can reach 115,200 baud in Windows 2000 as long as you set the baudrate in both the modem section AND the connection setting.
  • Since this is a direct cable connection, and no modem is actually being used on this machine at all, I'd just enter some duff data for this section.
  • Once you've got the null modem driver installed, point it to the port you've you the hotsync cradle on. In this case, COM1.
  • From within the "Network and Dial-Up Connections" section in control panel, select "Make New Connection".
  • Set it up to Accept incoming connections. (The "Connect Directly" setting is the opposite of what we are doing here, its the Win2k box doing what the Palm is doing in this instance)
  • Point the connection to the Null modem device we just setup. You can set the baud rate and other comms settings from the properties tab. Make sure Hardware flow control is set, and the hardware settings are 8N1.
  • Don't select allow VPN connections.
  • I've allowed my local user account to use the connection.
    However, after configuration of all this, I went back into the Users tab of the Incoming Connections entry in "Network and Dial-Up Connections" and checked the "Always allow directly connected devices such as palmtop computers to connect without providing a password". This means I don't have to stick a uid and password in the palm. If this is unchecked, and you do not provided the correct user id and password on the palm, you will get the error message "Error: incomplete setup. Check phone number & username. (0x121A)". Sticking the NT username and password will enable it to login. An advantage of this setting is during connection you will get an icon in the Network section with the user ID you've logged in as. Otherwise you'd just get the "Unauthenticated User" icon. A disadvantage is it appears the password is stored as plaintext within the NetworkDB palm database file. I used Insider V3.90.1 to have a look at the password for the Win2k connection made below and sure enough it was readable.
  • Put a couple of IP addresses in here. It needs a range of at least 2 to work. Make sure "Allow callers to access my local area network" is checked, otherwise you'll only be able to use resources on the Win2k box you're connected to.
  • If they ain't started already, start the "Remote Access Connection Manager" and "Routing and Remote Access" services from within the Services applet (Hidden in the Start\Programs\Administrative Tools\Services instead of the control panel). If you need to use normal directly connected HotSync you will have to stop the "Routing and Remote Access" service before firing up HotSync Manager. The same goes for shutting down HotSync Manager, or at least changing it from Local mode, once you've finished with it. (Thanks to Alik for pointing this out.). You can, as Ray Tran sugested, use Modem Sync for all your hotsync needs while connected over PPP.
  • That should be the Windows part setup. Remember to go back and check the "Always allow directly connected devices..." option if you aren't going to enter a password.

Palm Pilot Setup

As with the other Palm to ... articles on this site, the device is configured with a static IP address from the 192.168.2.* pool. I may try DHCP sometime in the future, but at present there is no need for it.
  • From the Network entry in Prefs, tap the phone number item and add 00 as the number. (This tells the pilot to access the serial port directly). Like unix, User id is not required, unless you really, really want to use it. Remember the palm seems to store it plain text.
  • Tap the details button and fill in the IP and DNS details. The DNS is again the FreeBSD machine, and the IP address is the same used by the unix pppd setup . If you've got a DHCP server on the network, you can check the Query DNS and auto IP checkboxes instead (thanks to Jeremy Sheeley for confirming this works)
  • The login script on the palm side needs to be:
    Send:		CLIENT
    Send:		CLIENT
    Wait for:	CLIENTSERVER


Now all you have to do is click connect...

If you have logging turned on for the serial port (recommended), you should see entries like these in the ModemLog_Communications cable between two computers.txt file in the windows directory:

03-25-2000 16:24:21.058 - Recv: CLIENT
03-25-2000 16:24:21.058 - Interpreted response: Ring
03-25-2000 16:24:21.058 - TSP(0000): LINEEVENT: LINE_NEWCALL
03-25-2000 16:24:21.058 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
03-25-2000 16:24:21.058 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
03-25-2000 16:24:33.065 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
03-25-2000 16:24:33.065 - TSP(0000): Closing Call
03-25-2000 16:24:43.991 - Recv: CLIENT
03-25-2000 16:24:43.991 - Interpreted response: Ring
03-25-2000 16:24:43.991 - TSP(0000): LINEEVENT: LINE_NEWCALL
03-25-2000 16:24:43.991 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
03-25-2000 16:24:43.991 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
03-25-2000 16:24:44.982 - Recv: CLIENT
03-25-2000 16:24:44.982 - Interpreted response: Ring
03-25-2000 16:24:44.982 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
03-25-2000 16:24:44.982 - TSP(0000): Answering Call
03-25-2000 16:24:44.982 - Answering the call.
03-25-2000 16:24:44.982 - TSP(0000): LINEEVENT: LINECALLSTATE_ACCEPTED
03-25-2000 16:24:44.992 - Send: CLIENTSERVER
03-25-2000 16:24:44.992 - Connection established at 19200bps.
03-25-2000 16:24:44.992 - Error-control off or unknown.
03-25-2000 16:24:44.992 - Data compression off or unknown.
03-25-2000 16:24:44.992 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
Without the second CLIENT send, the win2k box will sit idle for a few moments and then drop the line, as shown by this dump from the modem log.
03-04-2000 17:24:41.930 - Recv: CLIENT
03-04-2000 17:24:41.930 - Interpreted response: Ring
03-04-2000 17:24:41.930 - TSP(0000): LINEEVENT: LINE_NEWCALL
03-04-2000 17:24:41.930 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
03-04-2000 17:24:41.930 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
03-04-2000 17:24:53.617 - TSP(0000): Dropping call
03-04-2000 17:24:53.637 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
03-04-2000 17:24:53.637 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
03-04-2000 17:24:53.637 - TSP(0000): Dropping call
03-04-2000 17:24:53.637 - TSP(0000): Closing Call


Networking information

The ROUTE service seems to require the NETBIOSGROUP service installed and running (Thanks to Omric for pointing this out). This is generally installed with a network card. If you haven't got a network card, you may be able to install it by adding a modem and setting up an ISP connection.
Note: You may be able to get around this by unchecking the "Allow callers to access my local area network", although I haven't tested this.

Service Pack 1 information

A number of users have contacted me regarding a problem connecting various palm devices to Windows 2000 machines with service pack 1 installed. The serial port log will show the characters <ae> or <ae> instead of the usual CLIENT line. Jeremy Bailey has come up with the solution:
On the palm:
Home -> HotSync
(from top menu) Connection Setup
Direct Serial & Edit
Set Flow Ctl to "On", the default is Automatic
as soon as i changed that, it worked
also on this screen is the speed, which was set to 115,200
so i bumped up my win2000 speed and they are both using 115,200

On a related note, if anyone has had similar problems on Win2k Service Pack 2 and the above has fixed them, please drop me an email and I'll add the info to the page.

Windows 2000 Professional

It seems there is a bit of confusion over whether routing (the ability to get from the Palm to any other host on the local network or internet) works on Win2k Pro. I don't have a palm to test with at present, but be assured that as soon as I get a spangly new m500 (hurry up Palm!!) I'll investigate the problem. Meanwhile, several users have suggested various proxy type applications such as WinGate and WinProxyoffsite link to fill the gap.


USB connections ARE possible! But only at the moment to older palms (non mXYZ ones), when using the USB Kit that was available a while back. Thanks to Daniel Aguerrevere for the following information:-
Yes, it is possible, the USB kit installs a driver that translates
everything as the palm is connected to the COM4 (or the one available), just
when creating the null modem, instead of selecting COM1 or 2, you select

Compatibility with Pocket PC

Thanks to Corrado De Sanctis for pointing out that this will also work for PocketPC's too.

Multiple Palms

Yaron Ruckenstein is using an EdgePort USB to RS232 convertor ( This gives an additional 2, 4, or 8 COM ports and plugs into the host PC's USB port. It works on any port for one palm in Win2k Professional, and for more than one palm in Win2k Server.

RAS Admin tools

Libery Vance (sorry I've lost your email address) contacted me a while back with info on how to get more advanced logging through a built in MMC plug in for windows 2000. So, over to Liberty:
I went to the MSDN site, looked around to see how to enable the logging
of PPP, it pointed me towards the control panel under "Administrative
Tools", on to the "Routing and Remote Access" MMC plug-in.
Once in there I couldn't do much because I didn't have anything available
there. I Right-Clicked on the name of my machine in the left pane gave me
"Configure and Enable Routing and Remote Access".
I selected this and used the default option for configuration.
After that, I now have this in the right pane,
At this point the only step I took was, Right-Click on the Server Name
(local) in the left pane, and choose the Event Logging tab, along with
checking the "Enable Point-to-Point (PPP) logging".
This one step, configuring and enabling routing and remote access made
everything take off and start working for me


I recently got an MA600 IRDA adaptor working (finally) for bog standard IR transfers (address book and such), and have had a play around with trying to connect via an IR ppp connection. Unfortunately, I don't think it'll work with the base win2k load out, microsoft complain a bit about why at link however, someone proved them wrong and went and wrote a driver to sit on top of their IRDA stack at link Its payware so I don't know how effective it is.

Actually, I've just taken a look at the website and it's disappeared! In a frantic search for another URL to put in the bit above, try link which may or may not be of any help. (I haven't read it through yet.

Exciting news from two readers of this site:-

Mackie writes:
I have recently discovered that Nokia have released an IrCOMM update for windows 2000. The catch is that it will try and detect the nokia ir-enabled phone before it will install. I have a 7110 at it works great from my laptop. It is then possible to use this virtual comm port it sets up to talk to other devices (like my Motorola Timeport 250 and Palm III). It may be possible to get the update to install without a nokia phone, but I am not sure. The update is available from
Alex Morris writes that:
He has found a Windows 2000 irDA driver (Mark Moore also supplied a link to this site). It runs at 9,600bps, despite everything being set on the laptop and PDA for 115,200bps. Win2K runs the port at 115,200bps normally, so I'm guessing it could be a limitation of the driver.

Palm IIIe

Ray Tran reports that connections to a IIIe can work, if you let the connection manually timeout on the palm side. If you use disconnect, it seems quite difficult to force it to re-connect. Additionally (good point, this...) while you're connected this way, you need only select modem sync to use hotsync in conjuction with ppp connections.

Extra Uses

If you're handy with the old C++ compiler, PDA Developers have written a HTTP library which you can embed in to your own applications to chat away over the network link. An XML module is in the pipeline which opens up even more opportunities.

Back to Top Page last modified: 20 September 2002 08:19
Graeme Davisonemail link