Problem and question with TCP Post: 302934055

10 More Discussions You Might Find Interesting

1. IP Networking

tcp problem with port

I am trying to connect via DBACCESS and Informix server to a server on a different computer. When I execute the connect command from dbaccess I get the following message, Exec format error cannot bind a name to the port. As far as I know the port is not being used by another client. How...

2. IP Networking

WinXP and TCP/IP Problem

Hi Eveyone, I have A small problems maybe some one can help me. I'm running a small network at home with internet access. Two PC's have Win XP and one has Win98se. I have them all hook up on a SMC router. ALL windows firewall are off and and harddrive sharing is on. I am using DCHP network...

3. Solaris

TCP Problem

I am running a Java Client on Solaris 9 which communicates with the Server using TCP/IP. The client transmits a FIN packet to server. The server sends a ACK, FIN enters LAST_ACK state and then waits for ACK from client. The client did not respond back leaving the server in LAST_ACK itself. Also...

4. Programming

TCP status question

There is a server and a client,when client send a message to server,server can send a reply to client. The status of server and client is ESTABLISHED.Then I halt the client,I find the server status is CLOSE_WAIT and the client status is FIN_WAIT_2. Many minutes passed,I find the the server status...

5. Programming

C & TCP question: AF_INET vs AF_UNIX

Greetings! I am attempting to write a *basic* network client in C. I have manage to create a socket but I have doubts as far as using AF_INET vs AF_UNIX. At the present time, my client runs with AF_INET. Is AF_UNIX faster across hosts using the same OS flavor (Red Hat)? What is the difference...

6. Red Hat

tcp/ip problem

how the data from disk is loaded into memory and then it transfered to tcp/ip packet. how i can find how many pages are loaded into memory by that process what is the rate of context switch for that process.

7. Shell Programming and Scripting

tcp/ip and memory problem

how the data from disk is loaded into memory and then it supplied to tcp/ip packet. how i can trace the no of pages loaded in memory by that process and rate of context switch for that process.

8. Programming

Problem with tcp server

Hello @ all, I hope you can give me some advice :b: I will be following code for a tcp server and doStuff () function, the clients treated. From some point, I have several identical clients (zombies, I think), the same records in the database write. Has anyone an explanation? What can I...

9. IP Networking

Wireshark TCP and HTTP question.

Hello all. This is my first post and thank you for your forum. Here is my question. I have a simple setup at home and I was capturing some data with wireshark. Data between a workstation and the web server, requesting a page. Simple enough. Now when I open wireshark, I apply the TCP...

10. UNIX for Advanced & Expert Users

Bizzare TCP/IP problem

Hi all. I have a really really weird problem that I've been working on for days. The problem manifested as users cannot connect to our web servers via SSH when they're using our wireless network. Here's where it gets weird: - Clients from anywhere other than the wireless subnet can...

LEARN ABOUT DEBIAN

tcplisten

TCPCONNECT(1)						      General Commands Manual						     TCPCONNECT(1)

NAME

       tcplisten - general TCP/IP server

SYNOPSIS

       tcplisten [-irv] [localaddr] port

DESCRIPTION

       tcplisten  waits  for  a  TCP/IP connection on port.  If a localaddr parameter is given, tcplisten will bind to that IP address.  Otherwise
       tcplisten will accept connections to any of the local machines IP addresses.  Data received from the client is printed on standard  output,
       and  data  read	from  standard input is sent to the client.  When end-of-file is reached on both standard input and the TCP/IP connection,
       tcplisten terminates.

OPTIONS

       -i     Terminate at end-of-file on standard input; don't wait for the client to close the connection.

       -r     Terminate when the remote client closes the connection; don't wait for end-of-file on standard input.

       -v     Verbose mode.  Prints a message to standard error about the origins (host and port) of the client.

SEE ALSO

       tcpconnect(1), telnet(1), mini-inetd(1), tcpbug(1).

BUGS

       The names of the options are not yet finalized, and may change at a future release.

								   1997 April 13						     TCPCONNECT(1)