most tcp/ip terminal devices and routers contain a ping utility that sends an echo request packet to the designated device. the device then responds with an echo reply. troubleshooting a tcp/ip network is made easier by using the ping utility in your pc or workstation.

    procedure 8-5: testing the lan path to your firewall

    you can ping the firewall from your pc to verify that the lan path to your firewall is set up correctly.

    to ping the firewall from a pc running windows 95 or later:

    1.from the windows toolbar, click on the start button and select run.

    2.in the field provided, type ping followed by the ip address of the firewall, as in this example:

    ping 192.168.0.1

    3.click on ok.

    you should see a message like this one:

    pinging [ip address] 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

    if the path is not functioning correctly, you could have one of the following problems:

    1 wrong physical connections

    1 make sure the lan port led is on. if the led is off, follow the instructions in “local or internet port link leds not on” on page 8-2.

    2 check that the corresponding link leds are on for your network interface card and for the hub ports (if any) that are connected to your workstation and firewall.

    2 wrong network configuration

    1 verify that the ethernet card driver software and tcp/ip software are both installed and configured on your pc or workstation.

    2 verify that the ip address for your firewall and your workstation are correct and that the addresses are on the same subnet.

    procedure 8-6: 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 -n 10 [ip address]

    where [ip address] is the ip address of a remote device such as your isp’s dns server.

    if the path is functioning correctly, replies as in the previous section are displayed. if you do not receive replies:

    1 check that your pc has the ip address of your firewall listed as the default gateway. if the ip configuration of your pc is assigned by dhcp, this information will not be visible in your pc’s network control panel. verify that the ip address of the firewall is listed as the default gateway as described in “verifying tcp/ip properties” on page c-6.

    2 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.

    3 check that your cable or dsl modem is connected and functioning.

    4 if your isp assigned a host name to your pc, enter that host name as the account name in the basic settings menu.

    5 your isp could be rejecting the ethernet mac addresses of all but one of your pcs. many broadband isps restrict access by only allowing traffic from the mac address of your broadband modem, but some isps additionally restrict access to the mac address of a single pc connected to that modem. if this is the case, you must configure your firewall to “clone” or “spoof” the mac address from the authorized pc. refer to “manually configuring your internet connection” on page 2-12.