05-19-2008
Hmm, looks like you just get "Invalid argument" in $! if you use a host name which doesn't exist, so that doesn't help much. Still, a good habit to always include $! in suicide notes.
Connection refused means you forgot to start the listener on port 4343. You can't connect if nobody has opened the port for listening. Just run nc -l -p 4343 on there for now. Once you have the client working, you can work on replacing the server with something more to your liking.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower.
What i mean to say is since the send() function in the server program (it is... (2 Replies)
Discussion started by: rajesh_puru
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in?
Regards,
Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies
3. UNIX for Advanced & Expert Users
Hi Experts,
need help about release or refresh TCP Connection:
i have the sample like below :
application log connection:
0500 ( 192.168.0.1:36053) 00919 2007/05/10 23:30:25 112 13 2007/05/10 23:30:25 1969/12/31 17:00:00
0500 ( 192.168.0.1:36054) 00920 2007/05/10 23:30:26 000 00... (3 Replies)
Discussion started by: bucci
3 Replies
4. Programming
Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Discussion started by: raidzero
6 Replies
5. Solaris
Hello,
Actually there are some bugs in application which does not close the TCP connection to other server though CORBA.
We need to kill that ESTABLISHED connections as new connection are not happeneing as the allocated ports were used and showing as ESTABLISHED
Is there any... (4 Replies)
Discussion started by: GIC1986
4 Replies
6. UNIX for Dummies Questions & Answers
Dear experts,
I am seeing a lot of TCP failed connection attempts from "netstat -s" on one of our servers.
How can I pin point what connection failed and what are the ports involved?
Any tools/commands I can dig in deeper to diag. what went wrong on these "failed connection attempts"?
... (2 Replies)
Discussion started by: cache51
2 Replies
7. IP Networking
Why this happens?
How to solve this?
$netstat -na |grep 9325
tcp 0 0 127.0.0.1:9325 127.0.0.1:9325 ESTABLISHED
When a client socket repeatedly tries to connect to an inactive(no server socket is listening on this port) local port,connect succeeds.
... (1 Reply)
Discussion started by: johnbach
1 Replies
8. Solaris
Hi,
I use solaris Unix .
I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740
root@XX # netstat -an | grep CLOSE_WAIT | wc -l
285
root@XX # netstat -an | grep CLOSE_WAIT
10.158.35.4.34805 ... (2 Replies)
Discussion started by: abcdef
2 Replies
9. Programming
Hi.
I am writing client - server application using TCP sockets.
I need some very basic functionality, namely: how to check if another "participant" of the connection is still present?
I want to handle situations, when client is gone, or server breaks down, etc. (25 Replies)
Discussion started by: Shang
25 Replies
10. UNIX for Dummies Questions & Answers
I am trying to send json messages to a port on a linux server from a remote server running a .net program. I have one implementation running with successful incoming messages to port 1514. I tried to replicate the same thing but just to another port but cannot get it to work as I get the following... (3 Replies)
Discussion started by: unienewbie
3 Replies
DHID(8) BSD System Manager's Manual DHID(8)
NAME
dhid -- Dynamic Host Information System client.
SYNOPSIS
dhid [-h] [-p port] [-P pidfile] [-f conffile]
DESCRIPTION
dhid is the DHIS client daemon. After setting up with a DHIS provider, each machine may run a dhid daemon (in background) in order to update
its dynamic IP address within the server.
/etc/dhid.conf should be configured according to the provider's assigned parameters.
Once running, dhid sends echo request packets to the server and expects a reply. Once received, dhid tries to authenticate at the server
either in secure on insecure mode. From then on, and providing authentication was successful, the client waits and replies to queries origi-
nated at the server. If the server doesn't receive acknowledgments of these packets the host is marked offline. Likewise, if the client
doesn't receive queries for a period of time the offline stage is restored.
Therefore, the only thing a DHIS host needs is to run the dhid client. The server is able to determine when the host is online and the
server tables are updated automatically.
OPTIONS
-h Show usage information.
-p port
Specify port to listen on. If not specified, the default is port 58800.
-P pidfile
Use an alternative PID file instead of /var/run/dhisd.pid.
-l conffile
Use an alternative configuration file instead of /etc/dhid.conf.
FILES
/etc/dhid.conf
DHIS client configuration.
AUTHOR
dhid has been written by Joao Cabral <jcnc@dhis.org>.
This manual page was written by Guus Sliepen <guus@debian.org> for the Debian GNU/Linux system.
Debian GNU/Linux June 1, 2019 Debian GNU/Linux