Filter
Top Products
Chapter 5 95
Troubleshooting
Troubleshooting Client Connections
This indicates the client was unable to contact the Gateway. The
Gateway may be on a different subnet than the client (see your
Network Administrator) or the Gateway may have incorrect network
configuration values.
n For an HP-UX client system, type: ping hostname (or)
IP_address
Return. For example:
>ping E2050.agilent.com
PING E2050.agilent.com: 64 byte packets
64 bytes from 128.10.0.3: icmp_seq=0. time=8. ms
64 bytes from 128.10.0.3: icmp_seq=1. time=3. ms
64 bytes from 128.10.0.3: icmp_seq=2. time=3. ms
64 bytes from 128.10.0.3: icmp_seq=3. time=3. ms
Each line after the PING line is an example of a packet successfully
reaching the Gateway. If, after several seconds, ping does not print
any lines, use
Ctrl+C to kill ping. The ping command will then
report on what it found.
For example, the following indicates the client was unable to contact
the Gateway. The Gateway may be on a different subnet than the
client (see your Network Administrator) or the Gateway may have
incorrect network configuration values
----E2050.agilent.com PING Statistics----
7 packets transmitted, 0 packets received, 100% packet
loss
2 For an HP-UX client system ONLY, once ping works, you can try
one of the following rpcinfo commands using the Gateway IP
address to verify that the client has access privileges to the
Gateway (in the IP allow list configuration):
n rpcinfo -p IP_address Return. This rpcinfo command
gives the following response, where the line for program
395180 is the LAN server in the Gateway.
program
100000
100000
395180
vers
2
2
1
proto
tcp
udp
tcp
port
111 portmapper
111 portmapper
5055