Getting your PalmPilot Pro to talk PPP to Windows NT using Microsoft RAS
Notes:
- This works with the PPP Dialer support that is provided by USR in ROM on the PalmPilot Professional, and upgraded units. (More specifically, it doesn't work with the Dialer support that is provided by HandStamp from Smartcode Software.)
- This works for both Window NT Server and Workstation.
- I have only tried this with Windows NT Version 4.0, Service Pack 2. (Build 1381)
- I have had reports that this only works when both ends of the PPP connection are set to 19200 baud.
- You must be able to act as an Administrator of your Windows NT machine to make the necessary configuration changes.
- For other descriptions, see these pages:
- Configuring Window NT RAS for PalmPilot Pro
- PalmPilot de US Robotics (This one is in English.)
Disclaimers:
- These directions talk about modifying the security parameters of your Windows NT machine. This may weaken the security of your machine.
- These directions presume a fair degree of familiarity with configuration of Windows NT machines. If you aren't comfortable modifying your Network settings or changing permissions in the User Manager, then this is not for you. To some extent, these instructions are like a sharp knife. Use them carefully, and you won't get hurt.
- These directions work for me. Your mileage may vary.
On your Windows NT 4.0 machine
- Make sure you have IP Forwarding Enabled.
- Go to: Start | Settings | Control Panel | Network select the Protocols tab.
- Select TCP-IP Protocol.
- Choose Properties...
- Select the Routing tab.
- Make sure the Enable IP Forwarding checkbox is checked.
- Hit OK to close the Microsoft TCP-IP Properties dialog.
- Hit OK to close the Network dialog.
- Install support for RAS.
- Go to: Start | Settings | Control Panel | Network select the Services tab.
- Select Add...
- Choose Remote Access Service.
- Allow the software to install.
- Apply service pack 2. It is important that this be done after the RAS support has been installed. Service Pack 2 contains updated support for the RAS authentication. It allows for PAP authentication, using clear text. This is what the USR ROM PPP support uses.
- Configure the RAS support.
- Go to: Start | Settings | Control Panel | Network select the Services tab.
- Choose Remote Access Service and hit Properties...
- Hit Add... and select Dial-Up Networking Cable between 2 PCs.
- Choose an available COM port that you can connect your Pilot to. The COM port that the HotSync Cradle is plugged into will work. You just have to shut down the HotSync Manager before starting up the RAS service. And then, shutdown the RAS service before starting the HotSync Manager. Don't worry, NT won't let you start one when the other is running.
- Make sure that the Port is able to receive calls.
- From the Remote Access Setup dialog, Hit Network...
- Make sure that under Server Settings: only TCP/IP is selected.
- Hit the Configure button next to TCP/IP.
- I used the default settings. You may need to use other settings. See your network administrator if you aren't sure.
- Hit OK to close the RAS Server TCP/IP Configuration dialog.
- Under Encryption settings: select Allow any authentication including clear text.
- Hit OK to close the Network Configuration dialog.
- Hit Continue to complete the RAS setup.
- Create a RAS enabled user account using the User Manager.
- Go to: Start | Programs | Administrative Tools (Common) | User Manager
- Create a new user: User | New User...
- Fill in the fields, make sure you remember the Username and Password. You will need them when you configure the Pilot.
- Hit the Dialin button.
- Enable Grant dialin permission to user.
- Hit OK to close the Dialin Information dialog.
- Hit OK to close the New User dialog.
- Close the User Manager.
- Log into the newly created user account from the console at least once to complete the user account setup.
- Start the RAS service. You may have to shutdown the HotSync Manager to do this.
- Go to: Start | Programs | Administrative Tools (Common) | Remote Access Admin
- Start the server: Server | Start Remote Access Service...
- Select the current machine.
The following documents from the Microsoft Knowledge Base were helpful to me and may be informative for you:
On the Pilot in the Preferences, Network
- Create a new entry.
- Set the phone number to "00" (without the quotes). I have been informed that for PalmOS 3.3 there is ui support for setting the "Connection" to "Direct Serial". Note also that for PalmOS 3.3 it is important to ensure that the baud rates on Windows NT and the PalmPilot match.
- Set the user and password to the account you created on the NT machine that has RAS enabled.
- Tap Details.
- Set the Connection Type to PPP.
- Configure the appropriate primary DNS. See your network administrator if you aren't sure what this should be..
- Set IP Address to Automatic.
- Tap Script...
- Setup the following script:
- Send CR:
- Delay: 1
- Send: CLIENT
- Wait For: CLIENTSERVER
- End:
- Tap OK to close the Login Script dialog.
- Tap OK to close the Details dialog.
- Physically connect the PalmPilot to the COM port on your NT machine. Either by using a cable or by putting it into the cradle.
- Tap Connect
You can watch the progress of the connection by pressing the scroll down
hardware button while the Service Connection Progress dialog is active.
When you are connected, you can execute a variety of interesting commands
from the Network Log screen. It can be reached from the Network Preferences
by selecting the Options menu, and the View Log. Once you are in
the Log page, use Graffiti to enter a "?" and new-line to get help.
Once you have a direct PPP connection to your NT desktop, you can try
out programs like these:
Top Gun Telnet for the Palm Pilot Professional
NetNews for Pilot Pro 0.1a
Last updated: 03-Dec-2003 by greg@bentz.org