PPP Troubleshooting on the BeOS Preview Release
This document is a troubleshooting guide which attempts to answer some of themajor questions that people have been having surrounding PPP under the BeOSPreview Release. It is quite incomplete, but hopefully it will give you someguidance insolving your problem with PPP. This document is aimed at people using the BeOS Preview Release. If youare still using the DR8 release of the BeOS, check the guidelines for troubleshooting PPP under DR8 instead. This page was last updated on July 23, 1997. Please note that this document does not attempt to explain creating aPPP interface under the BeOS. The BeOS User's Guide, inthe section titled "NetworkInterfaces for Modem Connections" explains this process. If, after using the instructions to create a PPP Networkinterface, you are still having problems, it's time to start working ontroubleshooting. Generally, PPP problems (and solutions) can be broken down tothese areas:
Note: Some of the suggestions below require you to edit variousnetwork settings files manually. Whenever you edit any of these files, you needto openthe Network settings application, and click the "Restart Networking" button forthe changes you've made to the settings to actually take effect. Caution: More importantly, you need to back up any network settingsfile whenever you make manual changes. This is because if you ever make andsave changes using the Network preferences application, the settingsfile may be overwritten, and your manual changes will be lost.
You're Not Sure How to Use PPP The BeOS User's Guide for the Preview Release is available on the Be web site,in the Documentation section: http://www.be.com/documentation/index.html The relevant section to read for details of connecting your BeOS system to theInternet, including via a PPP connection, are in chapter 4 "Connecting the BeOSto the Internet," in the section "NetworkInterfaces for Modem Connections." You should definitely read the entirechapter, and particularly that section, to understand certain concepts aboutconnecting BeOS systems to the Internet. Here are a few quick tips about PPP that you might miss in the new User'sGuide:
It is possible that your modem cable is bad, or not wired correctly. A modernmodem cable is required for PPP to work properly. The cable should wire the RTS,CTS, and DTR lines. Many older cables do not correctly wire all of theselines. If you suspect that your modem cable could be bad, or incorrectly wired,borrow a friend's cable, or buy a new one at a store on the condition that youcan return it if it doesn't solve your problem. Connect your modem using the newcable, and try your PPP connection again.
The following modems are unsupported on the BeOS:
If you are trying to use PPP with any of these modems, you will be unable tomake it work. These are not true modems in the sense that portions of the modemhardware are emulated in software. This software runs under the Mac OS, butequivalent software has not (yet) been written for the BeOS. Further details regarding why thesemodems do not work under the BeOS can be found in the FAQ section of the website, if you're interested.
If you received a message like "can't open /serial/dev1", this means your serialport is in use by something else on your system, and so cannot be used by PPP.There are several possible reasons why this might be the case:
If you are not getting a dial tone when you try to initiate a PPP connection,or if your modem cannot connect to your ISP's modem, the problem is most likelyan incorrect modem initialization string. Different modems require different initialization strings. These strings setthe modem to the correct configuration for establishing the connection withthe service at the other end of the phone line. You choose the modem string byselecting your modem (brand and model) from the Modem pop-up menu in the PPPconfiguration panel dialog of the Network preferences application. If you do not find your modem in the pop-up menu, or if your modem is therebut does not seem to work, you will need to edit the file that contains theinitialization strings, and add a new modem/string combination to the file. Thisprocess is very simple:
To help you determine what initialization string to use, details regarding thesettings which must be enabled or disabled on your modem can be found in the BeOSUser's Guide: Changing the Modem Initialization String (even if theinstructions for how to do it are incorrect, the string you build will be thesame). If you cannot find the initialization string for your modem in the modemstring listing file, or the one you found doesn't work correctly, try using aninitializationstring for a different modem made by the same manufacturer. If even that fails, try looking for the initialization string in a connectionscript that successfully uses the modem on the Mac OS side (or on a Mac or PCusing that modem temporarily,should you be using a BeBox).
Modems Connect, Authentication Fails If your modem is in fact connecting to your ISP's modem pool, but theconnection is notgetting past the authentication process, then you most likely have an incorrect(for your ISP's particular PPP server) PPP connection script. This script ischosen by the Server Type pop-up menu of the PPP connection settings dialog. The PPP connection script handles sending your name and password (andsometimes aconnection protocol request) to the remote PPP server, in response to theserver's prompts. It works quite simply, waiting for the server to sendparticular strings, and then sending other strings back to the server. The first thing to try is changing the Server Type to either "Standard PPP" or"Unix login", whichever one you don't have chosen now. "Standard PPP"tells the BeOS to use PAP to log you in; "Unix login" uses amore traditional Unix style method to log in. If neither of those works, try anyother options you see, in order, except for the "Manual" option. Unfortunately, there is no universal script that will work with allPPP servers. The default scripts that come with the BeOS will work for many PPPservers,but not all. If none of the scripts work with your service provider, you can usethe "Manual" option, and log in manually every time, or you can write your ownPPP connection script. There are no easy steps to follow to do this, so we can only give you guidanceregarding writing a PPP connection script.You will need to either learn a fair amount about PPP login procedures, or workwith your ISP's technical support group, todetermine the exact script to use. You will probably find checking the "Display chat when connecting" checkboxto be extremely helpful in determining what your PPP connection script should be.Thiswill give you a small terminal window that appears when you connect, which willlet you seeexactly what the server is sending, and what the BeOS is sending back (whichmight not be working), and more importantly, it will let you figure out what theBeOS should be sending. PPP connection scripts are stored in a text file, located at Explanation:
Here are the special "escape codes", or tokens, which let you insert specialcharacters or character strings into the modem initialization string or the PPPconnection script (case matters with these, beware the upper and lower case"s"/"S" and "n"/"N" tokens!):
The Likewise the Note: The modem initialization string and the PPP connection scriptboth separate each string with aspace. If you need to actually send a command that includes spaces, you need to"escape" them using the
Other Problems and Problem-SolvingTechniques It is possible that your ISP is using dial-uphardware which does not implement its PPP support completely to thespecification. In this case, your modems would connect, but then nothing wouldhappen. Or perhaps you are having other problems that are not dealt with specificallyhere. Before you send in a request to Be's customer support department, you might trythe following (we'll ask you to try it when you contact us):
| |||
Copyright ©1997 Be, Inc.Be is a registered trademark, and BeOS, BeBox, BeWare, GeekPort, the Be logo and the BeOS logo are trademarks of Be, Inc. All other trademarks mentioned are the property of their respective owners. Icons used herein are the property of Be Inc. All rights reserved. Comments about this site? Please write us at webmaster@be.com. | |||