Troubleshoot A Tcp/Ip Network Using A Ping Utility; Test The Lan Path To Your Vpn Firewall - NETGEAR ProSafe FVS336Gv2 Reference Manual

ProSAFE Dual WAN Gigabit WAN SSL VPN Firewall FVS336Gv2
f. Make sure that an IPv6 address shows.
The previous figure does not show an IPv6 address for the computer but only a
link-local IPv6 address and an IPv6 default gateway address, both of which start, in
this case, with fe80.

Troubleshoot 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. You can
easily troubleshoot a TCP/IP network by using the ping utility in your computer or
workstation.
The following sections provide information about troubleshooting a TCP/IP network using a
ping utility:
•

Test the LAN Path to Your VPN Firewall

• Test the Path from Your Computer to a Remote Device
Test the LAN Path to Your VPN Firewall
You can ping the VPN firewall from your computer to verify that the LAN path to the VPN
firewall is set up correctly.

To ping the VPN firewall from a computer running Windows 95 or later:
1. From the Windows taskbar, click Start and select Run.
2. In the field provided, type ping followed by the IP address of the VPN firewall, for example:
ping 192.168.1.1
3. Click the OK button. A message similar to the following displays:
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 might have one of the following problems:
• Wrong physical connections
- Make sure that the LAN port LED is lit. If the LED is off, see
Functioning
- Check that the corresponding link LEDs are lit for your network interface card and
for the hub ports (if any) that are connected to your workstation and VPN firewall.
• Wrong network configuration
on page 612.
Diagnostics and Troubleshooting
620
Troubleshoot Basic