4. If both of the following are true:
vA problem occurs with your communications to the modem, or with
communications to or from the remote system (including connection script
problems)
vThe spooled file(s) for the point-to-point job does not contain enough
information to isolate the error
you may need to run a communications trace on the ASC line while attempting
the SLIP connection. When printing the trace data, be sure to specify *CALC for
the format of the data you are printing to allow the system to format both
EBCDIC and ASCII data properly.The communications trace could contain data
to help isolate the error that is occurring.
If you are not familiar with the procedure for collecting a communications trace,
refer to “Collecting a Communications Trace”on page 493 and “Formatting and
Saving the Communications Trace”on page 499.
5. If you are trying to connect to an Internet Service Provider (ISP) but are unable
to complete the connection, verify that no errors occurred up to the point the call
is made to the ISP.You can verify this through the Connection Dialog script
spooled output. Youshould see an entry for ‘Attempting modem dial/answer ’
followed by an ‘ATDT’(tone) or ‘ATDP’ (pulse) entry that contains the number
you are dialing.
If no errors occurred up to point when you dial your ISP,you may need to
contact your ISP to verify the following:
vIf you do not receive a ‘CONNECT’ indication after the call is made, verify
that the telephone number you are using for the ISP is correct.
vIf you need to dial another number to get to an outside line prior to dialing the
ISP,make sure that you use enough comma (“,”) special characters to allow
enough time for the outside line to become available. For example:
‘9,,,,7771234’ can be defined for the
Remote service phone number
in the
‘Remote system access information’ section of your point-to-point
configuration profile, where “9” is the number required to get an outside line.
The time delay for each comma is defined by your modem.
16 Wed May 1 13:37:48 1996 ==> CONNECT 19200 LAPM COMPRESSED
17 Wed May 1 13:37:48 1996 ==>
18 Wed May 1 13:37:51 1996 ==> login:
19 Wed May 1 13:37:51 1996 ==> sliptest8
20 Wed May 1 13:37:56 1996 ==> password:
21 Wed May 1 13:37:56 1996 ==> ********
22 Wed May 1 13:38:00 1996 ==> Access not authorized for user SLIPTEST8
23 Wed May 1 13:38:01 1996 ==> Remote host connection ended.
Figure 251. Connection rejection — Examples
16 Wed May 1 14:00:22 1996 ==> CONNECT 19200 LAPM COMPRESSED
17 Wed May 1 14:00:22 1996 ==>
18 Wed May 1 14:00:26 1996 ==> login:
19 Wed May 1 14:00:26 1996 ==> sliptest8
20 Wed May 1 14:00:31 1996 ==> password:
21 Wed May 1 14:02:36 1996 ==> Remote host connection ended.
Figure 252. Mismatches in Connection Scripts — Examples
Chapter21. TCP/IP Problem Analysis 441