This section identifies messages reported through the Ping application. Each message includes a description and suggests ways to resolve the problem.
Address already in use
Resolution: Using the Monitor application, show the Connection Table to verify that another application has the port number.
Broken pipe
Resolution: If the remote host has a logging facility, use it to determine why the connection was disconnected. Use any available network analysis tools to determine why the connection was disconnected.
Connection refused
Resolution: Make sure a server application is running on the target host that can accept the connection. Use available tools on the target host to display the connection table. Typical commands are netstat on UNIX hosts, and MULTINET SHOW/CONNECTIONS on VMS hosts using Cisco MultiNet for OpenVMS. Ask the network administrator if any access restrictions have been placed on the server application.
Connection reset by peer
Resolution: If the remote host has a logging facility, use it to determine why the connection was disconnected. Use any available network analysis tools to determine why the connection was disconnected.
Connection timed out
Resolution: Use the Ping application to verify that you have a route to the target host and that the target host is running.
Note
Firewalls often allow Ping to work but not other services such as Telnet or FTP. You may have to contact the network administrator for the remote host for assistance.
Couldn't contact DNS Server
Resolution: Verify that the IP address of the DNS server is correct, the DNS server is operational, and the network is operational.
DNS Server failure
Resolution: Verify that the DNS server is operational.
Host not found
Resolution: Verify the name was entered correctly. Verify that the host name and IP address are accurate in DNS.
Network is down
Resolution: Check the ODI, NDIS 2.0, or NDIS 3.0 configuration.
Network is unreachable
Resolution: Using the Configuration Utility, verify that the default route is correct in the Routing tab. Using network analysis tools on another machine, check the route that the packet takes to the remote network and verify that packets are being forwarded to the default gateway.
No Address for Host
Resolution: If your site uses DNS, use the Ping application to verify that the DNS name server is running and that your workstation can communicate with it. Using the Configuration Utility, verify that the IP address of the DNS server is correct. Verify with the DNS administrator that the host entry is in the DNS zone files. If your site uses host tables instead of DNS, verify that the host name and address for the target host are correct in the host table.
No buffer space available
Resolution: Make sure that your system has sufficient memory. Close any unused applications to free memory.
No Data in DNS Answer
Resolution: Use any available network tools to capture the DNS query and response. For additional help, please contact Technical Support.
No route to host
Resolution: Using the Monitor application, verify that the routing table is correct. Using the Configuration Utility, verify that the default route is correct in the Routing tab. Using network analysis tools on another machine, check the route that the packet takes to the remote network and verify that packets are being forwarded to the default gateway.
Not enough core
Resolution: Make sure that your system has sufficient memory. Close any unused applications to free memory.
Out of dynamic memory
Resolution: Make sure your system has sufficient memory. Close any unused applications to free memory.
HTML file generated May 15, 1996.