Press the Enter key. You should see a message like this one: Pinging with 32 bytes of data If the path is working, you see this message: Reply from < IP address >: bytes=32 time=NN ms TTL=xxx If the path is not working, you see this message: Request timed out 10-2 T r oubl es ho ot i n g Reference Guide for the Model RM356 Modem Router If the path is not functioning correctly, you could have one of the following problems: • Wrong physical connections – Make sure the LAN LED is on for the port attached to your PC. If the LAN LED is off, follow the instructions in “LAN Link LED” on page 10-1. – Check that the Link LED is on for the network interface card in your PC or workstation. • Wrong network configuration – Verify that the Ethernet card driver software and TCP/IP software are both installed and configured on your PC or workstation. – Verify that the IP address for your router and your workstation are correct and that the addresses are on the same subnet. Testing the Path from Your PC to a Remote Device After verifying that the LAN path works correctly, test the path from your PC to a remote device. From the Windows Run menu, type PING -t followed by the IP address of the remote device you are calling. If the path is functioning correctly, the OH (offhook) LED on the router should turn on, indicating that a call is being placed. If the OH LED does not turn on, follow these instructions: • Check that your PC has the IP address of your router listed as the default gateway. If the IP configuration of your PC is assigned by DHCP, this information will not be visible in the control panel network utility. Go to the Run… window and run winipcfg.exe (for Windows NT, run ipconfig.exe). The IP address of the router should appear as the Default Gateway. • Check to see that the network address of your PC (the portion of the IP address specified by the netmask) is different from the network address of the remote device. • Check Menu 12 and verify that at least one static route exists. As the call is being set up, your PC should display timeouts followed eventually by replies. If no replies are seen after one minute, the path is not functioning correctly. This response indicates that the router is unable to establish a PPP connection with the remote LAN. Refer to the next section, “Troubleshooting a Remote Node or ISP Connection.” To cancel the pings, type Ctrl-C (while holding down the Ctrl key, press the letter c). T r ou bl es hoot i n g 10-3 Reference Guide for the Model RM356 Modem Router Troubleshooting a Remote Node or ISP Connection To troubleshoot a remote node or an ISP connection, follow these instructions: • Place a manual call to the remote node, using Menu 24.4.5. The progress of the call is displayed on the screen. If the call does not connect, verify the following parameters in Menu 11: – Pri(mary) Phone # – Sec(ondary) Phone # • Verify your IP address in Menu 3.2 and verify the following parameters in Menu 11: – My Login – My Password – Rem IP Addr If the call is connected but quickly terminated, it indicates the possibility of a protocol negotiation problem. • Check the error log in Menu 24.3.1, which usually provides some indication of why the call was dropped. If there is nothing in the log, the call may have been dropped by the remote device. Verify that the configuration parameters between these two devices are consistent. If you are still unable to determine the problem, refer to “Using the Packet and Log Trace” on page 10-7. Troubleshooting a Remote User Connection To troubleshoot a remote user connection: 1. Verify that you configured the authentication parameters in Menu 13. These parameters are: – CLID Authen – Recv Authen – Mutual Authen 10-4 T r oubl es ho ot i n g Reference Guide for the Model RM356 Modem Router 2. Verify that the IP address is supplied correctly in Menu 13 if the remote dial-in user is negotiating IP. Check that the remote dial-in user is supplying a valid IP address and that the router is assigning a valid address from the IP pool. 3. Verify the user name and password for the remote dial-in user in Menu 14. If you are still unable to determine the problem, refer to “Using the Packet and Log Trace” on page 10-7. Troubleshooting the Manager Interface Refer to the following instructions if you cannot access the Manager interface by the serial port or by using the Telnet Protocol. If you cannot access the Manager interface by the serial port: 1. Verify that the router is connected to the serial port of your terminal or computer using the included cable. 2. Check the configuration parameters of your terminal or communications program. The connection should be configured as follows: – VT100 terminal emulation – 9600 baud rate (unless this setting has been changed previously in the router setup) – No parity, 8 data bits, 1 stop bit – No flow control If you cannot access the Manager by using the Telnet Protocol, refer to “Testing the LAN Path to Your Router,” on pag...
Log: