Filter
Top Products
ProSecure Web/Email Security Threat Management (STM) Appliance Reference Manual
Troubleshooting and Using Online Support 7-5
v1.0, September 2009
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 STM
You can ping the STM from your PC to verify that the LAN path to the STM is set up correctly.
To ping the STM from a PC running Windows 95 or later:
1. From the Windows toolbar, click Start and choose Run.
2. In the field provided, type “ping” followed by the IP address of the STM; for example:
ping 192.168.1.201
3. Click OK. A message, similar to the following, should display:
Pinging <IP address> with 32 bytes of data
If the path is working, you will see this message:
Reply from <IP address>: bytes=32 time=NN ms TTL=xxx
If the path is not working, you will 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 that the LAN port LED is on. If the LED is off, follow the instructions in
“LAN or WAN Port LEDs Not On” on page 7-3.
– 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 STM.
• 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 STM and your workstation are correct and that the
addresses are on the same subnet.