SCO UnixWare 7/OpenUNIX 8/OpenServer 6 FAQ : Networking :
Incoming PPP – UnixWare 7/OpenServer 6 Setup: The How-to Guide that works
tcalvert@oregonvos.net
Kudos: Thanks to Ryder Brooks of SCO's technical staff (and the tech support administration) for the time and education that provided the background for this instruction guide.
0. Preparation - what you'll need to get PPP dial-in working "Virgin" UnixWare 7 or OpenServer 6 system (a system that hasn't been 'messed' with in trying to setup incoming PPP). This is the best place to start. If you've tried to setup PPP and have failed, you may need to restore your settings to their default state before proceeding. (Notes on some of those are listed below). If you plan on logging in as 'root', keep your security level to low or traditional.
Hardware adequate to support your system. Our system is a "white box"
AMD K6/2
- 350 with 3 - 8GB IDE fixed disks, 1 - IDE CD-ROM, 192Mb RAM although we
initially installed the system with 1 - fixed disk, 1 - CD ROM and 64Mb
RAM.
The minimum patch list must be installed for UnixWare 7/OpenServer 6. In addition, patches related to iasy0 (serial communications), ping, ppp should also be installed even if not on the minimum patch list.
Ver 7.1.1 includes a number of patches (see TA 110731) to which we added ptf 7140a: Webtop upgrade to 1.41 ptf7601b - inet ptf7602c - xvfs ptf7603c - fs ptf7608b - sd01 ptf7612b - ping ptf7613a - iasy ptf7616a - specfs (A reboot / kernel re-link is required following most of these patches so this will take a while.)
There is also a patch to the /usr/lib/ppp/psm/ipexec.sh that must be applied for arp (TA110758).
At least one modem attached to the UnixWare 7/OpenServer 6 system. It is also nice to have your modem manual, as sometimes UnixWare 7/OpenServer 6 can't correctly identify your modem (e.g., in our site, a Wisecom 5614 may be identified as a Zoom V.34X - and the setup strings aren't the same)
A Windows (95 or later) system from which you can try the settings. Make sure that your modem can dial into another system (e.g., your ISP) before testing this. Make sure that you can log in using ppp - telnet access is inconclusive at this point. It may be that your modems are incompatible for running ppp - which will give not only false information but also headaches. Make sure that you have ins talled the current relevant patches for Windows: e.g., Dial up Networking 1.3 (MSDUN13), Internet Explorer 4.02 SP1, etc.
Your skill with UnixWare 7 or OpenServer 6 in using a text editor. You may need to edit some files.
------------ Note: Use of the term "UnixWare 7 or OpenServer 6" refers to Unixware 7.1 and later only. UnixWare and OpenServer are a trademarks of SCO, Santa Cruz Operations. Windows is a trademark of Microsoft Corporation.
Limitations: We have set up users to dial in and authenticate via PAP only, PAP and login, login only; we have not set up CHAP authentication. Realizing the danger of assuming, we anticipate that CHAP authentication would be identical to that of PAP with the same rules and limitations.
At this point, your UnixWare 7 or OpenServer 6 system should be running with the modem attached and you should be logged in at the console as root.
1. Add User Accounts Users may log into your system in two ways under UnixWare or OpenServer: as authenticating users only, or as Unix users. Authenticating users: - do not have valid Unix accounts with corresponding entries in /etc/passwd and /etc/shadow - only have entries for authentication in /etc/ppp.d/.pppcfg for PAP or CHAP and - PAP / CHAP entries are stored / recorded in plain text - are "invisible" to the system as far as licensing is concerned; do not "occupy" a license - are "invisible" to the system as far as monitoring is concerned; do not appear if the operator types "w" or "who" - cannot login to a shell account - cannot be logged in via a terminal window - may be detected automatically by the UnixWare or OpenServer system
Unix users: - have valid Unix accounts and can launch either character shells (e.g., ksh) or a ppp shell - may be authenticated via PAP, CHAP or login - occupy a license when connected - appear to the system via the "w" or "who" command - can spawn telnet, Webtop and Tarantella sessions - must login manually or via a script to launch ppp - cannot be detected automatically by the Unixware system
Decide now how you want your users to be authenticated and what options you want them to have:
If you want to eliminate all possibility of character logins and are willing to live with "invisible" users, select "Authenticating" users.
If you want to track users and make them visible to the system, if you need character based access to the system, select "Unix" users.
Why is this distinction important? PPP users can be authenticated by CHAP, PAP, login (Unix names/passwords) or a combination of these. Character-based users are only authenticated by logins. If you require PAP, then all users must authenticate - at least - by PAP regardless of anything else. You can theoretically require PAP for only some users: the .pppcfg file has sections for global bundle authentication and specific bundle authentication; however, if CHAP or PAP is required for one users, it is required for all.
For the illustration below, we'll set up a "hybrid" system to demonstrate both PAP and login authentication.
To add Unix Users: From the CDE desktop, open System Administration - General - Account Manager
Click on the leftmost button (the single person with "+") or Users - Add
Login: nppp This will be our Unix PPP User's name User ID: #### Comment: ppp user login Netware Login ID:
Login Shell: /usr/bin/pppsh You must manually change this from whatever the default is to this Home Directory: /home/nppp Login Group: other You might want to create a new group called "ppp users" via Group - Add then assign your ppp users to that login group Login Locale: System Default
Click on OK
On the Password screen, enter
Password: nppp It won't show Confirm: nppp
Click on OK
If you want to allow / limit your users to specific systems, you can click Users - Remote Access - but we'll leave that alone for now.
Exit from the Account Manager Files you've affected: /etc/passwd; /etc/shadow
2. Identify and install your modem
Before we begin: What is your modem name / type: _______________________________ What port is it connected to: COM1 = term/00m COM2 = term/01m COM3 = term/02m COM4 = term/03m Is it on a multi-port i/o card? Is it a multi-modem i/o card? Do you have the initialization strings for the modem or a setup script?
Our configuration is with a Wisecom modem, model FB WS5614ES3KV.
Click on Hardware - Modem Manager Your modem should not be displayed, so click on Modem - Add - Automatic Detection
Detect modems on serial port: 00m or whatever port you're connected to If you select ALL, then UnixWare or OpenServer may not find any modems.
Click on Detect, then OK
If it finds your modem: is what is found the correct type you have? If so, great. If not, then configure manually. If it doesn't find your modem, you must configure it manually.
Manual Configuration: Click on Modem - Add - Manual Modem Vendor: select the manufacturer Modem Model" select the model
Not found? Try vendor = Standard Modem Types Model = Standard 28800 bps Modem Select the port: term/00m
Configure port (same screen as below **) Port Type: Com 1 modem Configure Port: Incoming and Outgoing Incoming only may require modification of the /etc/saf/ttymon1/_pmtab file later on. Even if you're not going to dial out, select this one. Speed: 115200 (default) Port Settings: Data 8 (default) Parity None (default) Receive Buffer 8 (default)
OK
Check your changes in the /etc/uucp/Devices file: ACU term/00m,M - 115200 Standard_28800_bps_Modem
If your modem is not found or needs additional changes, you'll need to modify the following:
/etc/uucp/default/{name of modem config file} e.g., we want to create a file for Wisecom5614E, so we'll create a file with that name:
cp Zoom_V.34X Wisecom5614E vi Wisecom5614E (edit initialization strings as needed) :wq
create a link between the file you desire and the dialer ln /usr/lib/uucp/atdialer /etc/uucp/Wisecom5614E
/etc/uucp/Devices Add a line containing ACU term/00m,M - 115200 {name of link found in /etc/uucp }
If you manually configure your modem in this way, it won't show in the Modem Manager, and you may not be able to modify it except manually.
Check the permissions on your port: should be set to uucp:uucp chown uucp:uucp /dev/term/00m
Manually set up your modem via cu: #cu -l term/00m You type this Connected ATZ You type this: reset modem OK ATS0=1 You type this: answer on 1 ring OK AT&W You type this: save set things OK ~[hostname]. You type this: exit from cu #
Files affected:
/etc/uucp/Devices
/etc/uucp/default/{ }
/etc/uucp/{ }
3. Identify and install Serial port services Click Hardware - Serial Manager You should see:term00m::u:reserved:reserved:login:/dev/term/00m:boPhr:0:auto:60:115200_8N:ldter m,ttcompat:login\: :::::#
Port Logins Speed Description {icon} term/00m enabled 115200 COM 1 modem
Click on Port - Modify and you'll see the same screen as above (**) Verify your settings - sometimes if you change the speed or type of port, a change is made in one area but not another.
If you have made changes here, the sacadm and pmadm files make changes to ttymon and place those changes into the _pmtab file. Look at that file to verify your changes:
vi /etc/saf/ttymon1/_pmtab #Version=2
Check the current TAs: If your port is configured as incoming only and your timezone is not Ireland, you'll need to change :auto: to :/usr/bin/shserv: if you want a character login. Keep your port as bi-directional even if you are using it as incoming only.
Field 8 info: b = set bi-directional port flag o = initialize modem / reset via dials(3N) P = ppp flag h = sets hangup flag for ttymon r = wait for data before displaying a prompt c = set connect-on-carrier flag
There should be no need to modify these entries from the default seen above. If, however, you do, then you must then execute the following:
sacadm -k -p ttymon1 ; sacadm -s -p ttymon1
and wait about 3 minutes for the port to reinitialize.
Note: If you have multiple modems, you may find all of your modems controlled with ttymon1. This is normal and acceptable. If you have different types of modems (ACU, ISDN, etc), you must create separate ttymons for each type of modem. For maximum flexibility, each modem would be handled by a separate ttymon.
Files affected: /etc/saf/ttymon1/_pmtab
4. Configure DNS If you want your users to be able to use your system by name instead of number (e.g., www.yourcompany.com vs. 123.45.67.89) then setup DNS. This is not specifically required for incoming ppp access, it makes life a lot easier. If your system is to be used as an ISP, then you'll need more information than we can provide here. Our system is for dial-in, in-house only and does not function as a router to the internet; therefore, our ip address assignments are private and not routable.
Click on Networking - DNS Manager Click on Zones - Add Server type: Master Server type: Master Zone Name: {yourcompany.com} Networks: xxx.xxx.xxx Add
Start of Authority Person in charge root.{system name}.{yourcompany.com} Leave the rest of the entries at their defaults OK
For now, you can skip the remaining options for the Zone
Click on View - Records Add the systems you want your DNS server to know about - those on your local / remote network by clicking on Records - Add
Hostname: foo IP Addresses: xxx.xxx.xxx.xxx Add Leave the rest of the entries at their defaults for now OK
If you want to add a single alias for this host, you can add it here. Otherwise, you'll need to edit the /etc/hosts file.
If you want to install DHCP, now is a good time to do it. We didn't.
If you want to route packets through your Unixware system to the internet, enter the following at the prompt"
inconfig ipforwarding 1
Otherwise, your users will get to your system, see your web page and stay there.
5. Configure Dialin Services Manager Click on Networking - Dialin Services Manager
You should see a number of configured services on your system. Look for this one:
Type Device acu Any standard shell server
Click on Services - Modify to verify this entry:
Service: data over modem Device: Any you can limit this to a single port if desired Service path: standard shell server an option here is for ppp - it will work fine if you leave it alone. Phone number: any phone OK
Files affected: /etc/ics/Callservices
6. Configure Networking Services You may have already been here if your UnixWare or OpenServer system is part of a ethernet network. Click on Networking - Network Configuration Manager
After a delay, you'll see your ethernet / wired network information. Click on View - WAN.
You should see: Iasy0 COM1 modem (BIDIRECTIONAL)
Click on Software - Configure PPP (This is the heart of the ppp configuration and the area where the most problems / pitfalls occur.)
Do not use the Wizard. Instead, click on View - Bundles
>>>Creation of a PAP only bundle Click on Edit - Add Bundle name: in_pap Enabled: yes Type: incoming Options: Incoming Users: Auto-detect PPP session Yes This will listen on the line for ppp packets. This also requires some kind of authentication. Authentication: Edit Allow any valid authentication entry yes (Users may appear as "available" do not select them) If you select no to this question, then you may select individual users to allow in. OK This will place a "*" for the Authentication Name: Login Name: greyed out. Leave blank. Caller ID: leave blank Link Devices: Select COM1 ACU Incoming Authentication: Select PAP Override name for transmitted: leave blank Override name for received: leave blank Time allowable: 60 Network Protocol: Select IP Edit Options: IP Local address assignment: by local and remote cannot override Local address: xxx.xxx.xxx.xxx IP address of your UnixWare or OpenServer system
NOTE: this should be the actual address of your UnixWare or OpenServer system, although you may assign an additional IP for your UnixWare or OpenServer system to handle this ppp connection
Remote address assign: by local and remote cannot override Remote address: xxx.xxx.xxx.xxx IP address of your dial-in system. This may or may not be its actual address, but for the ppp connection, this is the address.
NOTE: if you assign an address that refers to an existing in-house system, that machine may find itself "locked out" of your internal TCP/IP network. It is safer to assign a dummy address for the remote (e.g., 192.168.0.79) to protect your internal addresses.
Use as default route: No If you answer Yes, you're telling UnixWare or OpenServer to use the incoming system as the route instead of the existing LAN. Act as a gateway: Yes Act as proxy for ARP: No Network Mask: xxx.xxx.xxx.xxx OK Options: Filters Bring up filter: bringup Keep up filter: keepup Pass in filter: blank Pass out filter: blank Advanced Options: VJ compression (Header compression in Win 98) Use VJ Compression: Yes Use slot compression: No Number of available slots: 16 Advanced Options: DNS Advertise DNS addresses: supplied addresses Advertised primary DNS: xxx.xxx.xxx.xxx Address of your UnixWare or OpenServer system acting as DNS master Advertised secondary DNS: blank unless you have one Get address of DNS servers: Yes Advanced Advanced: (leave at default values)
Advanced Options: Link Protocols CCP available - none selected Advanced Options: Multilink (leave at default values) Advanced Options: Advanced (leave at default values) Advanced Options: Bandwidth (leave at default values) OK You should now see:
+ in_pap (authentication name *)
double click on the + to see
- in_pap (authentication name *) IP (local: xxx.xxx.xxx.xxx)(remote: xxx.xxx.xxx.xxx)(gateway) COM1 (node: /dev/term/00m)(type: ACU)
>>>Creation of a Unix Login bundle - This will also require PAP authentication
Click on Edit - Add
Bundle name: incoming
Enabled: yes
Type: incoming
Options:
Incoming Users:
Auto-detect PPP session No
Authentication: leave blank
Allow any valid authentication entry no
(Users may appear as "available": do not
select them)
If you select no to this question, then you
may select individual users to allow in.
OK
Login User Name: Edit
Allow any PPP user: Yes
A list of unix - ppp users will show as
available. Do not select them.
OK
This will place a "*" next to Login User Name
Caller ID: leave blank
Link Devices:
Select COM1 ACU
Incoming Authentication:
Select NONE
--------------------------------
NOTE: If you go back and check Incoming Authentication for your in_pap bundle,
it will have changed to NONE - because the GUI apparently only reads the last
setup for Incoming Authentication in RAM rather than in the file. Because of
this, check your /etc/ppp.d/.pppcfg file:
global bundle {
requirepap = enabled should require PAP on
all incoming calls
bundle in_pap {
requirepap = enabled this is required
bundle incoming {
requirepap = disabled this allows unix users
to dial in and ask for
ppp
When you check Incoming Authentication, you'll see the state selected for
whatever one was last selected. When the file is written, the setting may
not be correct; therefore, check the .pppcfg file. If necessary to make
changes, see section 10 - 8.
-----------------------------------
Override name for transmitted: leave blank
Override name for received: leave blank
Time allowable: 60
Network Protocol:
Select IP
Edit
Options: IP
Local address assignment: by local and
remote cannot
override
Local address: xxx.xxx.xxx.xxx
IP address of your UnixWare or
OpenServer system
Remote address assign: by local and remote
cannot override
Remote address: xxx.xxx.xxx.xxx
IP address of your dial-in system.
This may or may not be its
actual address, but for the ppp
connection, this is the address.
Use as default route: No
If you answer
Yes, you're
telling UnixWare
or OpenServer
to use the
incoming system
as the route
instead of the
existing LAN.
Act as a gateway: Yes
Act as proxy for ARP: No
Network Mask: xxx.xxx.xxx.xxx
OK
Options: Filters
Bring up filter: bringup
Keep up filter: keepup
Pass in filter: blank
Pass out filter: blank
Advanced Options: VJ compression (Header
compression in Win 98)
Use VJ Compression: Yes
Use slot compression: No
Number of available slots: 16
Advanced Options: DNS
Advertise DNS addresses: supplied addresses
Advertised primary DNS: xxx.xxx.xxx.xxx
Address of your UnixWare or OpenServer
system acting as DNS master
Advertised secondary DNS: blank unless
you have one
Get address of DNS servers: Yes
Advanced Advanced:
(leave at default values)
Advanced Options: Link Protocols
CCP available - none selected
Advanced Options: Multilink
(leave at default values)
Advanced Options: Advanced
(leave at default values)
Advanced Options: Bandwidth
(leave at default values)
OK
You should now see:
+ incoming (login *)
double click on the + to see
- incoming (login *)
IP (local: xxx.xxx.xxx.xxx)(remote:
xxx.xxx.xxx.xxx)(gateway)
COM1 (node: /dev/term/00m)(type: ACU)
Now add your PAP secret for each user you give login priviledges to:
Create a PAP only user:
Click on View - Authentication
Edit - Add
Name: ppp1
Enable CHAP secrets: no
Enable PAP secrets: yes this defines the user as needing
PAP authentication
Enable login password: no this defines the user as a
non-unix user
Secrets: PAP
Local password: ppp1 or whatever you want
Remote password: leave blank
OK
OK
Add PAP to Unix User
Select user nppp created above
Click on Edit - Modify
Enable CHAP secrets: no
Enable PAP secrets: yes
Enable login password: yes
Secrets: PAP
Local password: nppp this must be the same as the
login password:
Windows only has a place for a single password, so CHAP, PAP and login
password must all be the same.
OK
Create a new Unix user
Click on Edit - Add
Name: {enter a login name here}
Enable CHAP secrets: no
Enable PAP secrets: yes
Enable login password: yes
Secrets: PAP
Local password: {password} this must be the same as the
login password:
Windows only has a place for a single password, so CHAP, PAP and login \
password must all be the same.
Secrets: login
Enter password: {password}
Confirm password: {password}
OK
This makes an entry into /etc/passwd
Files affected:
/etc/ppp.d/.pppcfg
/etc/passwd
/etc/shadow
Now is a good time to shutdown and restart the UnixWare or OpenServer System, so that your settings are clean.
7. Setting up debugging for the system?
Add debugging to the pppd by
#ps -e | grep pppd
xxx TS 70 pts/0 0 00 pppd xxx is the process
id number
#kill -9 xxx
#pppd -d 6
To make this permanent, edit the /etc/rc2.d/S71ppp file and modify the
line
$PPPD -d 6
^^^^^ new
Debugging log is /var/adm/log/ppp.log
If the login fails due to lack of secrets, check in step 6 above.
If the login succeeds, but you can't ping or get your browser going,
it may be a Windows / Modem issue.
8. Configure the Windows 9x / NT / 2000 / XP / 2003 / Vista system for dial-out
Set up a new dialup networking connection with the following parameters:
Login to network: no yes will also work.
Enable Software compression: yes
(remainder of options) no you may want to create a log
of the session...
Server Types:
NetBEUI no
IPX/SPX no
TCP/IP yes
TCP/IP settings
Server assigned IP address
Server assigned name server addresses
Use Header compression yes
Use default gateway yes
If you are using only PAP authentication and you are not a Unix user, you
can jump to step 9.
If you are a Unix user, you must create / modify a login script because
Unixware can't detect that you want ppp when you call in:
Click on Scripting Tab
Click on Browse
Select pppmenu.scp
Click on Edit
Make the following changes:
"
integer nLoginTimeout = 3
string szPW = "password:"
integer nPWTimeout = 3
boolean bUseSlip = FALSE
; -----------------------------------------------------
; Delay for 1 second
delay 1
transmit "^M^M"
; Attempt to login at most 'nTries' times
while 0 < nTries do
; Wait for the login prompt before entering
waitfor szLogin then DoLogin
until nLoginTimeout
TryAgain:
transmit "^M" ; ping
nTries = nTries - 1
endwhile
goto BailOut
DoLogin:
; Enter user ID
transmit $USERID, raw
transmit "^M"
; Wait for the password prompt
waitfor szPW until nPWTimeout
if FALSE == $SUCCESS then
goto TryAgain
endif
; Send the password
transmit $PASSWORD, raw
transmit "^M"
; Wait for the prompt
waitfor szPrompt
transmit szConnect
set ipaddr getip 2
endif
goto Done
BailOut:
; Something isn't responding. Halt the script
; and let the user handle it manually.
set screen keyboard on
halt
Done:
endproc
Yes, you can remove any lines beginning with ";" to make the script
smaller.
File - Save As and use the name ppp.scp
Now browse and select ppp.scp for your login script.
9. Test the Connection
With your modem on and ready to receive on the UnixWare or OpenServer system, dial in from your Windows machine.
If you are using the PAP only user, enter the name 'ppp1' and the
password 'pass
word' in the dialup networking dialog box. Do not open a terminal screen to
see what is happening - you won't get in. Unixware is supposed to autodetect
ppp under this setup and a terminal screen doesn't send ppp packets.
If you are using the unix - PAP login with a script, you can use a terminal
screen to login manually and verify that ppp packets are being transmitted.
You can also press F7 to continue and let the script log in and see what
happens.
10. Troubleshooting, or "Take 2 aspirin and call me in the morning"
There are hundreds of settings possible and some cascade into multiple levels
of errors. To help out with troubleshooting, examine these areas:
UNIXWARE ISSUES
1) External Modem: Is your UnixWare or OpenServer modem on?
Does it answer the phone? Some internal multi-modem cards have a 2 minute
timeout following an unsuccessful login attempt. If the initialization
strings are not set properly, the modem won't answer. Check sacadm -l to see
if ttymon is running on your port.
2) Can you login as a character - unix user? Create a unix user using the
default settings for everything, then attempt to log in via Hyperterm. If
you can't log in, deal with the modems / UnixWare or OpenServer settings first.
3) Have you made changes to _pmtab that have not been implemented? Make
sure you leave field 8 containing "obPhr" and field 10 as "auto". If you
need to restart ttymon1, use this command:
sacadm -k -p ttymon1 ; sacadm -s -p ttymon1
4) Have you installed all of the minimum updates to UnixWare or OpenServer? If not, return to step 0.
5) "Sometimes UnixWare or OpenServer ppp just gets confused with so many settings." Are your configuration files as clean as possible? Notice that we didn't link a specific input to a specific port. We could have specified ppp shell in serial and modem services, but we let the /etc/passwd file handle that.
6) Double check your modem settings / initialization (our Wisecom modem
was identified as a Zoom and it didn't work properly because it didn't
initialize properly). Sometimes you'll need to turn off the modem, turn
it back on and, perhaps, reinitialize it. (External modems are easier to
use at this point.)
7) Did you edit the /etc/ppp.d/.pppcfg file manually? If so, you must load
the settings into ppptalk via
cat /etc/ppp.d/.pppcfg | ppptalk
ppptalk save
and if the settings conflict within the file, don't blame us or SCO - they
tell us not to change the file manually.
8) If you can log in but can't get past the UnixWare or OpenServer system -- are the addresses you're using routable through the internet? If you use 192.168.x.x as addresses, they aren't. Did you turn on ipforwarding in /etc/inet/inet.dfl?
9) If one user needs PAP or CHAP, all users do. Check your authentication
requirements again. If you have both Unix-ppp and PAP only users, Unix-ppp
users will fail if their PPP secrets don't exist. PAP users will fail if you
disable PAP authentication because they aren't Unix users.
10) If you have made changes to files, have you killed and restarted the
daemons?
11) Some things just go together: Autodetect PPP requires authentication
and will let any authentication work, as long as it is PAP or CHAP, and
confuses logins for unix users. As above, you can create two bundles - one
for PAP users and one for login users; however, all users must use PAP
authentication because PAP is checked during the link phase which preceeds a
user being attached to a bundle.
12) Check your package permissions if you see misc errors, such as "initprivs"
on the console. Use the following sequence when logged in as root to fix the
permissions (see help for initprivs):
cd /
pkgchk -fv all
initpriv
If this doesn't handle the errors, the next command will sync the security
databases with the files:
/etc/security/tools/setpriv -x
13) If you connect but can't ping or get a browser to load the Unixware
home page, check to make sure that your ppp connection is active:
netstat -r
ifconfig -a
15) If you have pppd debug turned on, look at the /var/adm/log/ppp.log
file - make sure that:
The user has authenticated properly
The phase network has started
That ipexec.sh has added ppp0 then "up" 'd it
(We found that the ppp connection was made and was added, but was timing out
due to Windows or a modem being unable to send / receive ppp packets.)
16) We found that users can log in better if the console isn't running the
CDE GUI. In a few instances, once users had logged in, the console stalled
when loading Xsco. In another instance, we found a defunct process
immediately below the
Xsco in the pid listing which may have been associated with the "frozen" Xsco.
In addition, the CDE GUI was taking about 20% of available RAM on a 128MB RAM
system. (These situations have not been researched rigourously - these are
tentative observations.) Restarting startx resulted in Xsco running and
creating a defunct progess again. Try resetting the system, NOT
logging in to the GUI and log in to an alternate console (CTRL-ALT-F2) in
character mode. (A long term solution might be to add more RAM.)
WINDOWS ISSUES
17) Is your Windows system "clogged up"?
Check your temp folders and remove any temporary files you find.
Check your internet cache folders and remove cache files.
Run scandisk and check your drive for lost clusters.
Any files in the root directory ending in *.chk (such as FILE0001.CHK)? If
so, remove them. How much free space is on your fixed disk (at least 15% of
the total volume or more is recommended / required)?
Does your fixed disk need to be defragmented? If you've run Windows for over
a week, then the answer is "yes".
Are you running any other programs at the same time you're trying to dial in?
Is your Windows Registry filled with invalid references (some utilities can
find invalid registry entries and remove them)?
Does the Registry need to be cleaned and defragmented?
Any of the above can affect the performance of a Windows system.
18) Have you installed all of the patches / updates to Windows? If not,
return to step 0. We have successfully completed ppp log ins to our
Unixware system from Win95B with DUN 1.3 installed, Win98, Win98 2nd Ed.
using generic modems and laptops. Others have used Windows 2000 systems to
successfully dial in.
19) Try dialing in from another Windows system. Perhaps the modem or Windows
TCP/IP installation on one system isn't working properly. On one of our
systems, we could not log in from Win 98, ISA 33.6 modem. We switched to a
56K V.90 PCI modem and still couldn't get in. We cleaned the system
(16 above) and still couldn't get in. Finally, we turned off "log into
network" and turned on "create a log file for this connection" in the dial-up
properties - and successfully connected. Immediately after disconnecting,
we reversed these settings and have still been able to get in.
20) Is your dial-out Windows modem an x.2 and the dial-in Unixware modem a
v.90 (modem incompatibilities)? Are your setup-strings in Windows correct
for the modem? Is the driver for the modem the correct one? Have you tried
to reinstall the modem as a "Standard 28800 Modem" or "Standard 56000 Modem?"
Sometimes the "Standard" settings work better than the drivers bundled with
the modem.
21) If you can't login, recheck your login and password. Are you trying to
login with a PAP only authentication and using a modem script? Are you trying
to login as a Unix user with PAP without a modem script?
22) One user who has a winmodem could not log in, even after a clean
reinstall of Windows 98 2nd Ed. Other users who didn't have winmodems
had no problems, once the script files / dial-up settings were established.
PHONE ISSUES
23) Never underestimate the power of a noisy phone line. Try reducing the
speed of the modem on the Windows side (Unix should match the speed).
#
16416
2 Setup Incoming PPP connections to Unixware 7.1x or OpenServer 6
How do I set up bidirectional PPP?