07-08-2010
TCP does best-effort delivery, which is why it has such obnoxiously long timeouts. I've seen it survive 10-minute network outages. It's really not designed to do what you want. Try pinging your host to see if it responds or not.
10 More Discussions You Might Find Interesting
1. Solaris
Hi all
This is my first post in this forums. I hope some one can help me with this
my Sun Ultra 60 worked fine couple of months back when i used a dell (1280x1024). i move to a MN last month n bought a new sony monitor with (1280x1024) but when i connect it to the box it monitor displays... (1 Reply)
Discussion started by: venuavula
1 Replies
2. Programming
Hello everyone. Thanks for reading. I am using Ubuntu 7.04 to experience this problem:
I have written my own programs that communicate to eachother and I am having a hard time detecting a TCP socket disconnect when the remote side's computer has a power-failure (for example).
On the computer... (6 Replies)
Discussion started by: pjwhite
6 Replies
3. Red Hat
hi..
I unplug my eth0 lan cable.. and suddenly my system shutdown... no idea :eek::confused: (3 Replies)
Discussion started by: flekzout
3 Replies
4. IP Networking
Hi, I am trying to implement a server-client socket communication. My server and clients are in different PCs. During communications if the ethernet cable is removed from the server side it shows broken pipe due to unable to write on the socket. I want to know how to check whether the ethernet... (0 Replies)
Discussion started by: JagadishB
0 Replies
5. IP Networking
Hi,
I'm trying to communicate two servers (HP DLProliant 380 G5) via a crossover cable, but I don't get them to ping each other.
I am working in RHEL 4.
These are the steps I've performed:
1) Plugged the crossover cables in eth2.
(note: The cable is brand new. Also I built one myself... (3 Replies)
Discussion started by: jrodriguez365
3 Replies
6. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
7. AIX
Hello,
Is there any API or any other approach to detect whether the network cable is connected to the network adapter, say, en0, en1 or en2?
The OS is AIX6.1.
Thank you. (4 Replies)
Discussion started by: zephyrbj
4 Replies
8. Programming
Hello!
I searched forum for similar topic, with no luck, if you know one, delete this topic, and send me private message with link please.
Little background:
I have a lot of clients and one serwer. Client can make multiple connections on different ports and ips, but only one can be acctive... (2 Replies)
Discussion started by: ikeban
2 Replies
9. IP Networking
Hello,
Our software is using a TCP socket (AF_INET, SOCK_STREAM) to communicate with an Ethernet device. When we send a message, the message object writes itself in full onto the socket's stream buffer before the software invokes send() from socket.h.
I'm still researching, but have 2... (1 Reply)
Discussion started by: bix_20002000
1 Replies
10. IP Networking
Hello,
I detect these errors in my logs :
Socket timeout calling url http://server:port/bla/soap/selfcare/infoRapide]
Unable to make proxyRequest
I've made a tcpdump capture this way :
tcpdump -i eth0 -s 0 -w /app/captura.pcap port 8080
But I'm fairly new in reading .pcap files with... (0 Replies)
Discussion started by: black_fender
0 Replies
LEARN ABOUT REDHAT
rusers
RUSERS(1) BSD General Commands Manual RUSERS(1)
NAME
rusers -- who is logged in to machines on local network
SYNOPSIS
rusers [-al] [host ...]
DESCRIPTION
The rusers command produces output similar to who, but for the list of hosts or all machines on the local network. For each host responding
to the rusers query, the hostname with the names of the users currently logged on is printed on each line. The rusers command will wait for
one minute to catch late responders.
The following options are available:
-a Print all machines responding even if no one is currently logged in.
-l Print a long format listing. This includes the user name, host name, tty that the user is logged in to, the date and time the user
logged in, the amount of time since the user typed on the keyboard, and the remote host they logged in from (if applicable).
DIAGNOSTICS
rusers: RPC: Program not registered
The rpc.rusersd(8) daemon has not been started on the remote host.
rusers: RPC: Timed out
A communication error occurred. Either the network is excessively congested, or the rpc.rusersd(8) daemon has terminated on the
remote host.
rusers: RPC: Port mapper failure - RPC: Timed out
The remote host is not running the portmapper (see portmap(8) ), and cannot accomodate any RPC-based services. The host may be down.
SEE ALSO
rwho(1) users(1), who(1), portmap(8), rpc.rusersd(8)
HISTORY
The rusers command appeared in SunOS.
BUGS
The sorting options are not implemented.
Linux NetKit (0.17) August 15, 1999 Linux NetKit (0.17)