topic Re: ping occasional request timeout problem in Operating System - HP-UX

ping occasional request timeout problem

ddramos — Sun, 22 Feb 2004 22:05:31 GMT

hi guys,

i am trying to ping myself "ping " and occasionally gets a "request timeout" although very seldom, but i'd like to get an explanation as to why this happens.

please advise.

thanks,
ddr

Re: ping occasional request timeout problem

Steven E. Protter — Sun, 22 Feb 2004 23:26:19 GMT

Lots of possible reasons:

The IP address could be on two workstations on the network.

There could be a cable thats twisted a little too much and theres an intermittant problem.

The cable could be bad.

The NIC card could be flakey.

The Router could be misconfigured.

The Switch could be misconfigured.

There could be an IOS problem on the router.

The network could be overloaded and not properly subntetted.

SEP

And lots of other things.

SEP

Re: ping occasional request timeout problem

ddramos — Mon, 23 Feb 2004 00:04:53 GMT

Hi Steve,

Thanks for the prompt reply, would the switch, cables or switch be of concern even if i'm just doing a ping to myself? how can i check whether my NIC card is flakey or not?

Regards,
DDR

Re: ping occasional request timeout problem

ddramos — Mon, 23 Feb 2004 00:28:40 GMT

Hi Steve,

Just a short history, the ip address i am using was previousely used with another server that we replaced but i already configured this server with another IP.
By the way here's a piece of info i found from syslog.log of my new server with ping problem. Kindly verify and advise. Thanks.

Jan 10 09:50:04 AMXDB1 sshd[796]: Server listening on 0.0.0.0 port 22.
Jan 10 09:50:04 AMXDB1 rpcbind: check_netconfig: Found CLTS loopback transport
Jan 10 09:50:04 AMXDB1 rpcbind: check_netconfig: Found COTS loopback transport
Jan 10 09:50:04 AMXDB1 rpcbind: check_netconfig: Found COTS ORD loopback transport
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: check binding for udp
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: check binding for tcp
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: check binding for ticlts
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: check binding for ticotsord
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: check binding for ticots
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: ticlts: address in use
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: ticots: address in use
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: ticotsord: address in use
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: ticlts: address in use
Jan 10 09:50:07 AMXDB1 above message repeats 3 times
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: ticots: address in use
Jan 10 09:50:07 AMXDB1 above message repeats 3 times
Jan 10 09:50:04 AMXDB1 rpcbind: init_transport: ticotsord: address in use
Jan 10 09:50:07 AMXDB1 above message repeats 3 times
Jan 10 09:50:18 AMXDB1 xntpd[1199]: tickadj = 625, tick = 10000, tvu_maxslew = 61875
Jan 10 09:50:18 AMXDB1 xntpd[1199]: precision = 9 usec
Jan 10 09:50:18 AMXDB1 pwgrd: Started at Sat Jan 10 09:50:18 2004, pid = 1209
Jan 10 09:50:23 AMXDB1 diagmond[1251]: started
Jan 10 09:50:23 AMXDB1 /usr/sbin/envd[1256]: restart, and read the configuration file
Jan 9 20:50:40 AMXDB1 krsd[1675]: Delay time is 300 seconds.

Regards,
Danny

Re: ping occasional request timeout problem

Abdul Jaffar — Fri, 27 Feb 2004 05:03:17 GMT

Hello DDR
Does the non response withing ur server not happening at particular time or it is random.

1.Check the autonegotiation setting of the lan card.Use lanadmin--->lan--->display
2.Try that particular time #ping 127.0.0.1
3.Does the ip is dynamic or static.If static check any duplicate presence.
4.check you have latest ARPA /network patches.