Operating System - Tru64 Unix

Re: ETIMEDOUT

 
George R. White
Advisor

ETIMEDOUT

What would cause an ETIMEDOUT (Connection timed out), where the local and remote IP are the same but different port numbers? AS 8400 running Tru64 Unix 5.1b, never seen problem running 4.0F. Is there any way to gather more info to determine exactly what the problem is?

6 REPLIES 6
Al Licause
Trusted Contributor

Re: ETIMEDOUT

Can you please provide more information such as which application are you using and which are you attempting to connect to ?

Are you connecting to "localhost" or the actual hostname/ip_address of the system ?

Is this a standalone system or a cluster and if a cluster, please state whether you are connecting to the hostname/address or cluster alias.

A complete error message may also help as well as any logged information.

George R. White
Advisor

Re: ETIMEDOUT

We are connecting to a localhost. This is a standalone system. We are using FTLAN.

Lxxxxxx.c: Connection timed out.
l_addr=<192.168.0.1,4102> r_addr=<192.168.0.1,6000>

192.168.0.1 IP address of host getting message displayed above.



Ralf Puchner
Honored Contributor

Re: ETIMEDOUT

if ip of local network adapter: network outage.

It depend also on used protocol (udp/tcp) and system utilization.
Help() { FirstReadManual(urgently); Go_to_it;; }
George R. White
Advisor

Re: ETIMEDOUT

Could this be a driver problem?
George R. White
Advisor

Re: ETIMEDOUT

The problem is that it reconnects, and then later we get another "Connection timed_out".

Al Licause
Trusted Contributor

Re: ETIMEDOUT

I'm not familiar with FTLAN, but from the port it's connecting to, it sounds like an X application ?

Is this the only application that behaves in this way ?

Are you able to telnet, ftp, ssh, rlogin or make any other type of connection w/o
problems ?

Have you tried tcpdump to see just what sort of response the host is providing ?