#VIDEO TOOLS PING WINDOWS#
Use the Windows command line on your client computer to test DNS resolution. If your ping to the default gateway of the Firebox external interface fails, verify these possible causes:
#VIDEO TOOLS PING HOW TO#
For details about how to do this, go to the preceding Network Troubleshooting Tools section. To verify that outbound traffic to the Internet goes through the Firebox, enable logging of allowed packets in the ping policy and verify that log messages are created for ping requests from your network. If your network has an Internet gateway other than the Firebox, Internet-bound traffic from clients on your network might not be routed through the Firebox. You can view the IP address of the Firebox external default gateway in WatchGuard System Manager, or in the Interfaces dashboard in Fireware Web UI. This confirms that your computer can route to a host outside the Firebox, and that your Firebox is configured to allow these ping requests. To test this, from your Windows computer try to ping the default gateway for the Firebox external interface.
If you can successfully ping the IP address of the Firebox interface, test whether traffic from the client computer can be routed to addresses outside the Firebox. Test 2 - Ping the Default Gateway of the Firebox If the ping gets a response when the network is not connected to the Firebox interface, some other host on the network uses an IP address that conflicts with the IP address of the Firebox interface. To test this, disconnect the cable from the Firebox interface and then try to ping the internal interface of the Firebox from a client computer.
If the problem affects all or many users on your network, it could be that there is an IP address conflict between the Firebox internal IP address and another device on your network. Look at the ipconfig command output and consider these possible causes for the ping failure: To view the IP address and default gateway in local network configuration on a client computer, from the Windows command prompt, use the ipconfig command. If you are cannot ping the internal IP address of the Firebox, this could indicate a problem with the configuration on the Firebox, or a problem with your local network configuration or cabling. To start a ping from a Windows computer, use the instructions in the preceding section. For example try to ping a local network server, or the IP address of a Firebox internal interface. Test 1 - Ping an Internal IP Addressįrom your local computer, try to ping other internal IP addresses on the same local network. Use the instructions in the previous section to run the diagnostic commands used in these tests and to look at log messages. If that is successful, the next step is to test routing and DNS resolution to hosts outside your local network. To identify the cause of Internet connection problems from computers on your local network, start with ping tests from a local computer on your network to the Firebox or a local server on your network.
0 kommentar(er)
