07-15-2011
From adminschoice.com:
Quote:
This occurs either when the destination host is down or when
problems in the network cause lost transmission.
First check the operation of the host system, for example by
using ping(1M) and ftp (1), then repair or reboot as necessary.
If that doesn’t solve the problem, check the network cabling and
connections.
No connection was established in a specified time. A connect or
send request failed because the destination host did not properly
respond after a reasonable interval. (The timeout period is
dependent on the communication protocol.)
It usually means you never sent all the data to start with, or no data at all.
The problem is on the ubuntu side probably.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am scp'ing a file from a server (servera) to my server (serverb)
If servera is down - the scp never times out ... it just hangs eternally..
It is possible to specify a timeout in my script - so if scp fails/hang for more than 60 seconds I assume its failed ?
I am aware there is some... (3 Replies)
Discussion started by: frustrated1
3 Replies
2. HP-UX
Hello,
We try to do an SCP of a Sybase dump file of 4Go between two production HP-UX servers.
Each time the transfer stopn at 299Mo and we have the message "connection lost".
The destination FS has largefiles option activated.
Could you help ? (7 Replies)
Discussion started by: ohemeg
7 Replies
3. UNIX for Advanced & Expert Users
Hello,
I was wondering is there a way for SCP to shorten the timeout to fail when it attempts to connect a host that is down. Seems like it takes about a minute or so for scp to timeout. This is on a AIX 5.3 box.
I saw someone suggest use -o ConnectTimeout but the scp I use doesn't have that... (1 Reply)
Discussion started by: benefactr
1 Replies
4. UNIX for Dummies Questions & Answers
hi people,
i need help about timeout duration of ssl while connecting to another server in network.
this is what i try
bash-3.00# time ssh root@10.10.10.10 "date"
ssh: connect to host 10.10.10.10 port 22: Connection timed out
real 3m10.215s
user 0m0.007s
sys 0m0.011sthere is no... (2 Replies)
Discussion started by: sdkbjk
2 Replies
5. UNIX and Linux Applications
Hi
I am trying to configure sendmail for logwatch and another script i have . However when i try to send a test mail i am getting the following error.
Logwatch is not sending any emails out nor is denyhost. I just want it to send emails out .
Can anyone help me ?
i have looked through... (1 Reply)
Discussion started by: um08
1 Replies
6. UNIX for Advanced & Expert Users
Does anyone know a way to keep the connection open with scp? I really don't like having to type my password in every time I want to transfer a file. Or is there another similar program that will keep my connection open? (6 Replies)
Discussion started by: cokedude
6 Replies
7. Solaris
i am facing an issue that the server give a connection timeout after 60 sec for any request more than that number . i tried to increase the TCP INTERVAL TIMEOUT from the default 60000 ms to more higher number.
the server seems to work fine and didn't give me the massage of the timeout but the... (0 Replies)
Discussion started by: core99
0 Replies
8. Shell Programming and Scripting
Hi,
I am running a ssh connection test in a script, how can I add a timeout to abolish the process if it takes too long?
ssh -i ~/.ssh/ssl_key useraccount@computer1
Thank you.
- j (1 Reply)
Discussion started by: hce
1 Replies
9. Shell Programming and Scripting
Hi Team,
I have 2 servers Server-A & Server-B.
Is there any way to test scp connection between Server-A & Server-B without transferring file?
Basically i want to test the availability of scp connection..
Thanks in advance... (6 Replies)
Discussion started by: Girish19
6 Replies
10. Red Hat
HI
We have some Red Hat Linux Sevres which is having TCP connection timeout, not SSH connection, as an example oracle connection connected from TOD.
SSH i managed to add keepalive and it's working fine (1 Reply)
Discussion started by: bentech4u
1 Replies
ARPD(8) BSD System Manager's Manual ARPD(8)
NAME
farpd -- ARP reply daemon
SYNOPSIS
farpd [-d] [-i interface] [net ...]
DESCRIPTION
farpd replies to any ARP request for an IP address matching the specified destination net with the hardware MAC address of the specified
interface, but only after determining if another host already claims it.
Any IP address claimed by farpd is eventually forgotten after a period of inactivity or after a hard timeout, and is relinquished if the real
owner shows up.
This enables a single host to claim all unassigned addresses on a LAN for network monitoring or simulation.
farpd exits on an interrupt or termination signal.
Note: The program name farpd has been changed in Debian GNU/Linux from the original name (arpd) to avoid name clash with other ARP daemons.
The options are as follows:
-d Do not daemonize, and enable verbose debugging messages.
-i interface
Listen on interface. If unspecified, farpd searches the system interface list for the lowest numbered, configured ``up'' interface
(excluding loopback).
net The IP address or network (specified in CIDR notation) or IP address ranges to claim (e.g. ``10.0.0.3'', ``10.0.0.0/16'' or
``10.0.0.5-10.0.0.15''). If unspecified, farpd will attempt to claim any IP address it sees an ARP request for. Mutiple addresses
may be specified.
FILES
/var/run/farpd.pid
SEE ALSO
pcapd(8), synackd(8)
BUGS
farpd will respond too slowly to ARP requests for some applications. In order to ensure that it does not claim existing IP addresses it will
send two ARP request and wait for a reply. This slowness affects the nmap network scanning tool, and possibly others, which uses by default
ARP when scanning local networks. The answers from farpd will come after the tool has timeout waiting for the ARP replies and, consequently,
IP addresses claimed by farpd will not be discovered.
Additionally, farpd sends the ARP replies to the broadcast address of the network and not to the host that send the ARP request. Some systems
and applications (notably nmap) will not handled these requests and expect directed ARP replies (i.e. targeted specifically to the host that
sent the request and not to the network)
AUTHORS
Dug Song <dugsong@monkey.org>, Niels Provos <provos@citi.umich.edu>
August 4, 2001