How do I interpret 'netstat -a' output?

0.0.0.0 usually refers to stuff listening on all interfaces. 127.0.0.1 = localhost (only your local interface) I'm not sure about ::.

0.0.0.0 usually refers to stuff listening on all interfaces. 127.0.0.1 = localhost (only your local interface) I'm not sure about :: TIME_WAIT means both sides have agreed to close and TCP must now wait a prescribed time before taking the connection down. CLOSE_WAIT means the remote system has finished sending and your system has yet to say it's finished.

127.0.0.1 is your loopback address also known as 'localhost' if set in your HOSTS file. See here for more info: en.wikipedia.org/wiki/Localhost 0.0.0.0 means that an app has bound to all ip addresses using a specific port. MS info here: support.microsoft.com/default.aspx?scid=... '::' is ipv6 shorthand for ipv4 0.0.0.0.

Not answering your question but have you ever used a tool like TCPView from sysinternals. Much better than messing with a cmd window.

Send-Q is the amount of data sent by the application, but not yet acknowledged by the other side of the socket. Recv-Q is the amount of data received from the NIC, but not yet consumed by the application. Both of these queues reside in kernel memory.

There are guides to help you tweak these kernel buffers, if you are so inclined. Although, you may find the default params do quite well.

0.0.0.0 indicates something that is listening on all interfaces on the machine. 127.0.0.1 indicates your own machine. :: is something I don't have, but my machine does have *:* which shows that UDP ports don't really have a foreign address - they receive packets from any where.

That is the nature of UDP. How should each part of the foreign address be read (part1:part2)? Part1 is the hostname or IP addresspart2 is the port.

For those seeing :: in their netstat output, I'm betting your machine is running IPv6; that would be equivalent to 0.0.0.0, i.e. Listen on any IPv6 address.

This might also be OS-specific. On my Mac OS X system, by default, IPv6 is on, but the IPv6 ("tcp6") entries still say ". " – benc Jul 23 '09 at 6:02.

This link has helped me a lot to interpret netstat -a A copy from there - TCP Connection States Following is a brief explanation of this handshake. In this context the "client" is the peer requesting a connection and the "server" is the peer accepting a connection. Note that this notation does not reflect Client/Server relationships as an architectural principal.

Connection Establishment The client sends a SYN message which contains the server's port and the client's Initial Sequence Number (ISN) to the server (active open). The server sends back its own SYN and ACK (which consists of the client's ISN + 1). The Client sends an ACK (which consists of the server's ISN + 1).

Connection Tear-down (modified three way handshake). The client sends a FIN (active close). This is a now a half-closed connection.

The client no longer sends data, but is still able to receive data from the server. Upon receiving this FIN, the server enters a passive close state. The server sends an ACK (which is the clients FIN sequence + 1) The server sends its own FIN.

The client sends an ACK (which is server's FIN sequence + 1). Upon receiving this ACK, the server closes the connection. A half-closed connection can be used to terminate sending data while sill receiving data.

Socket applications can call shutdown with the second argument set to 1 to enter this state. State explanations as shown in Netstat: State Explanation SYN_SEND Indicates active open. SYN_RECEIVED Server just received SYN from the client.

ESTABLISHED Client received server's SYN and session is established. LISTEN Server is ready to accept connection. NOTE: See documentation for listen() socket call.

TCP sockets in listening state are not shown - this is a limitation of NETSTAT. For additional information, please see the following article in the Microsoft Knowledge Base: 134404Â NETSTAT. EXE Does Not Show TCP Listen Sockets FIN_WAIT_1 Indicates active close.

TIMED_WAIT Client enters this state after active close. CLOSE_WAIT Indicates passive close. Server just received first FIN from a client.

FIN_WAIT_2 Client just received acknowledgment of its first FIN from the server. LAST_ACK Server is in this state when it sends its own FIN. CLOSED Server received ACK from client and connection is closed.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.