Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Windows has a feature called .NET TCP Port Sharing which allows different .NET applications to share the same TCP/IP port.

I would like to monitor the source and destination connections of each client and associate them to the relevant server side listener. How do I reliably & efficiently accomplish this?

share|improve this question
First time I've come across this net.tcp thing (not being a windows user). It sounds like a nightmare anti-pattern. Thanks microsoft. – lynks Dec 14 '12 at 14:48
Can you request that it is reported to your systems by in-app code?… – jimbobmcgee Dec 14 '12 at 16:56
netstat on the server to determine host IP and source port along with the binary/PID serving the request? – schroeder Dec 19 '12 at 20:21

I think the only real audit you can do here is to actually turn the service off. Besides that I think the only limit you can set are the authorized security identifiers (SIDs) which can be configured (as described here on msdn).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.