Filter
Top Products
v If your user ID or password information is being rejected, verify that the
correct user ID and password are configured in your point-to-point
configuration profile and that this information is correct for your ISP account.
v Verify that the connection script you are using matches what the ISP is
expecting. The connection dialog script spooled file output and a
communications trace of the failed connection attempt may help with this
verification.
Problem: SLIP Job ’Hung’ with STRSSN Status
If you start a point-to-point profile and the status on the WRKTCPPTP display for
the profile appears to be hung at a STRSSN status, this could be an indication that
an inquiry message has been sent to the system operator (QSYSOPR message
queue) and the job is waiting for a reply. Go to a command line and enter the
following command:
DSPMSG MSGQ(QSYSOPR)
Look for inquiry messages involving the ASC line in use. If you find messages, look
for information on the problem that is occurring. Typical problems include:
v The modem is powered off
v The modem cable is not connected properly.
Before continuing, either answer the inquiry message or end the SLIP session by
issuing the ENDTCPPTP command. After ending the session, correct the problem
and try to start the session again.
Problem: SLIP Connection Complete but Unable to PING
If you cannot PING REMOTE IP address:
v Try setting the WAITTIME parameter on the PING command to a value greater
than the one second default.
Dial-up connections are much slower than direct connections through LANs and
some other types of connections. The default wait time for the PING command is
one second, which may be too short a time period for the PING to complete over
the dial-up line.
If you cannot PING LOCAL IP address:
v If you can PING the remote IP address (showing connectivity to the remote
system) but cannot PING the LOCAL IP address, then it is unlikely that there is a
problem. It depends on how the remote system is configured. If the remote
system is capable of forwarding IP datagrams and has its routing set up correctly
to send the IP datagrams back to your local address, the PING should work. But,
if the remote system cannot forward IP datagrams or its routing is not set up to
send the IP datagrams back to your local address, the PING request will not
work. This is because of the way PING works on point-to-point links.
v Refer to “Allow IP Datagram Forwarding” on page 145 for more information on
why the remote system must forward IP datagrams to be able to PING your local
IP address.
Materials Required for Reporting SLIP Problems
Include the following with any SLIP problem reported to IBM:
1. The type of remote host, operating system, and operating system level.
442 OS/400 TCP/IP Configuration and Reference V4R4