User`s guide

Troubleshooting
Problems accessing the remote network
D-10 Preliminary January 30, 1998 Pipeline User’s Guide
Connection profile. Try enabling PAP or CHAP for the Recv Auth parameter
so that the Pipeline matches the caller’s name to the Station parameter in a
Connection profile and gets the corresponding LAN Adrs.
Problems accessing the remote network
If, when you press Ctrl-D in the Configure profile, the status window in the upper
right corner displays a message other than LAN Session Up, you should first
disconnect the Pipeline from the phone line connection, reconnect it, then try
accessing the remote network again. If you still cannot access the remote
network, one or a combination of the following may be a problem:
• Your Pipeline may not be installed correctly.
• Your Pipeline may not be configured correctly.
• Your phone line may not have been activated, or there may be a problem
with the telephone network.
Check the installation
1
Make sure your Pipeline is connected to your phone line.
2
Check the WAN LED on the front panel of your Pipeline.
If the WAN LED is not blinking, continue to the next section, “Configuration
problems” on page D-11.
If the WAN LED is blinking, one of the following may be the case:
– Your Pipeline may not be connected to the phone line.
– If you do not have an integrated NT1 interface, your Pipeline may not be
connected to an NT1.
– Your phone line may not be activated.
– Your ISDN channel may be temporarily unavailable.
– You may have entered an incorrect switch type. Check the setting in the
Configure profile.
– You may have entered the wrong SPID. Check the setting in the
Configure profile, and confirm the values with your service provider.
3
Check to make sure you have connected your Pipeline to your ISDN line.