05-22-2008
First, test that the client connects correctly. Run netcat on a random port on the server and change the client to connect to that port (let's say 4343 again for old times' sake).
For debugging, you might want to change the client code to die with a diagnostic if print fails, and also add a close and die if that fails.
On the server, make a debugging version of the CGI which prints something useful to standard output as well (which will be served up back to the connecting client), so you can see that it runs. Connect to it with your browser and check that you get the results you expect.
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
LEARN ABOUT ULTRIX
rlogind
rlogind(8c) rlogind(8c)
Name
rlogind - remote login server
Syntax
/etc/rlogind
Description
The server is used for the program. The server provides a remote login facility with authentication based on privileged port numbers.
The server is invoked by when it receives a connection on the port indicated in the login service specification. For further information,
see When a service request is received, the following protocol is initiated:
1. The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2. The server checks the client's source address and requests the corresponding host name. If the hostname cannot be determined, the dot-
notation representation of the host address is used.
Once the source port and address have been checked, allocates a pseudo terminal and manipulates file descriptors so that the slave half of
the pseudo terminal becomes the stdin, stdout, and stderr for a login process. For further information, see
The login process is an instance of the program, invoked with the option. The login process then proceeds with the authentication process
as described in but if automatic authentication fails, it reprompts the user to log in on a standard terminal line.
The parent of the login process manipulates the master side of the pseudo terminal, operating as an intermediary between the login process
and the client instance of the program. In normal operation, the packet protocol described in is invoked to provide ^S/^Q type facilities
and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and terminal type, as
found in the environment variable, TERM. For further information see
The screen or window size of the terminal is requested from the client, and any changes in the window size from the client are sent to the
pseudo terminal.
Restrictions
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but it is
useful in an open environment.
Diagnostics
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1.
Hostname for your address unknown
No entry in the host name database existed for the client's machine.
Try again
A fork by the server failed.
/bin/sh: ...
The user's login shell could not be started.
See Also
rlogin(1c), inetd(8c)
rlogind(8c)