Way to show list of all open sockets on a Windows server and the socket properties

socketwindows 7

We are using a third party library in one of our applications. We would like to find a tool which will list all of the open sockets on the machine AND give us the ability to see the various TCP properties associated with the socket suck as:
SendBufferSize
ReceiveBufferSize
NoDelay (Nagle)
DontFragment
TTL

We've spoken to the vendor, and although they have disabled Nagle on their server, we would like to know exactly how the sockets are being created with their library on our servers.

Any tools out there for this?

Best Answer

I don't know if this is a solution for you, but i read this post where they use Wireshark/Netmon to show/monitor delays in TCP packets to detect whether Nagle is used or not: http://blogs.msdn.com/b/windowsazurestorage/archive/2010/06/25/nagle-s-algorithm-is-not-friendly-towards-small-requests.aspx

(i'm not allowed to post comments so had to put this in an answer..)

Related Solutions

The difference between Unix sockets and TCP/IP sockets

A UNIX socket, AKA Unix Domain Socket, is an inter-process communication mechanism that allows bidirectional data exchange between processes running on the same machine.

IP sockets (especially TCP/IP sockets) are a mechanism allowing communication between processes over the network. In some cases, you can use TCP/IP sockets to talk with processes running on the same computer (by using the loopback interface).

UNIX domain sockets know that they’re executing on the same system, so they can avoid some checks and operations (like routing); which makes them faster and lighter than IP sockets. So if you plan to communicate with processes on the same host, this is a better option than IP sockets.

Edit: As per Nils Toedtmann's comment: UNIX domain sockets are subject to file system permissions, while TCP sockets can be controlled only on the packet filter level.

Linux – the linux command to find out the number of socket currently open

I agree, this should probably be on ServerFault.

But, until then:

The issue with what you are doing is the watch command. Watch repeats a command so that you can see the output again and again over time.

My lsof doesn't accept a -4 argument, but if yours does, then

sudo lsof -i -4 -a -P | wc -l

Works for me.

Best Answer

Related Solutions

The difference between Unix sockets and TCP/IP sockets

Linux – the linux command to find out the number of socket currently open

Related Topic