Server Fault is a question and answer site for system and network administrators. 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

When a client communicates with the server, the destination port of the traffic sent to the server, is say x, while the source port is a random number say y. While establishing multiple connections with server on the same the destination port & IP address, can it be tied to the same source port & same IP address? Is this possible? If yes, can you give any example?

share|improve this question

No. The combination of [SourceIP]:[SourcePort] <-> [DestinationIP]:[DestinationPort] has to be unique for each TCP or UDP connection so for TCP or UDP there can only be one connection per tupelet.

The TCP and UDP protocols are separate though, so TCP port N and UDP port N are entirely different. This means that you could have connections that appear to share the same [SourceIP:SourcePort] and [DestinationIP:DestinationPort] as one is TCP and the other is UDP, however because of the protocol difference they don't.

share|improve this answer

Although IP / Port has to be unique on each end of the connection, the server will be LISTENING on a specific address / port, when the server ACCEPTS the connection it will be accepted on a DIFFERENT port. This is how the server can handle many different clients at the same time.

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.