Troubleshooting A Tcp/Ip Network Using A Ping Utility; Testing The Lan Path To Your Firewall - NETGEAR ProSafe FVG318 Reference Manual

Reference Manual for the ProSafe Wireless 802.11g VPN Firewall Model FVG318
• Your PC may not have the firewall configured as its TCP/IP gateway.
If your PC obtains its information from the firewall by DHCP, reboot the PC and verify the
gateway address.

Troubleshooting a TCP/IP Network Using a Ping Utility

Most TCP/IP terminal devices and firewalls 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 very easy by using the ping utility in your PC or workstation.

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 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.1.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:
• Wrong physical connections
— Make sure the LAN port LED is on. If the LED is off, follow the instructions in
or Internet Port LEDs Not On" on page
— 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.
Troubleshooting
10-2".
v1.0, October 2005
"LAN
10-5