Re: Changing listener ports

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for the information, one last question. Why would a server create
ephemeral ports for one connection, but use a single port for another? The
two clients on our side connecting to this server are very similar, Dell
Poweredges.


"Arkady Frenkel" wrote:

> No, that nature of TCP stack
> Arkady
>
> "Mark Perschbacher" <MarkPerschbacher@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:C88501CB-BDF2-4FF0-BC93-15128C3C2C10@xxxxxxxxxxxxxxxx
> > Is there a way to disable the use of ephemeral ports?
> >
> > "Alexander Nickolov" wrote:
> >
> >> Read about ephemeral ports. In TCP terms it's a client, even
> >> though on higher application level it may be considered a server.
> >> So you have a TCP client that connects to a TCP server and
> >> your TCP client uses ephemeral ports that keep increasing
> >> until at some point they wrap over.
> >>
> >> --
> >> =====================================
> >> Alexander Nickolov
> >> Microsoft MVP [VC], MCSD
> >> email: agnickolov@xxxxxxxx
> >> MVP VC FAQ: http://www.mvps.org/vcfaq
> >> =====================================
> >>
> >> "Mark Perschbacher" <MarkPerschbacher@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> >> message news:828FC3C4-8C89-4141-A2C5-D4C1D7EF1E7E@xxxxxxxxxxxxxxxx
> >> > So you are saying that the server side is creating these temp. local
> >> > ports?
> >> >
> >> > "Farooque Khan" wrote:
> >> >
> >> >> It must be incrementing the local port, not the port on which the
> >> >> server
> >> >> is
> >> >> listening. For each connection that a client makes, the server will
> >> >> create
> >> >> sockets with temporary local ports which keep incrementing. These will
> >> >> be
> >> >> releived (in TIMED_WAIT state) after some specific time.
> >> >>
> >> >> --
> >> >>
> >> >> -Farooque
> >> >>
> >> >>
> >> >> "Mark Perschbacher" <Mark Perschbacher@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >> >> wrote
> >> >> in
> >> >> message news:279A1A22-EEF1-44F5-8929-D181EFC28998@xxxxxxxxxxxxxxxx
> >> >> > We are attempting to send data from a Win 2003 server to a UNIX
> >> >> > system,
> >> >> > and
> >> >> > have no problem connecting with TCP/IP. Data is passed fine, then
> >> >> > at
> >> >> > some
> >> >> > point, our server starts incrementing the listening port number up.
> >> >> > Even
> >> >> > though netstat -an shows us as ESTABLISHED, on the remote server
> >> >> > side,
> >> >> > they
> >> >> > show three connections, the most recent port number ESTABLISHED, and
> >> >> > the
> >> >> > other two in TIMED_WAIT. Why do you think our server is changing
> >> >> > port
> >> >> > numbers?
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Netzwerkproblem GBit -> 100MBit
    ... GBit-Kette - flow control zwingend notwendig sei. ... zwischen Client und Server. ... Das kann TCP an der Stelle nicht mehr leisten. ...
    (de.comp.sys.novell)
  • suspect bug in vge(4)
    ... The high-level view of the problem is that the client seems to stall ... HTTPS server. ... not only printed for TLS/SSL issues but simply also for broken TCP ... To me it sounds like a broken implementation of hardware generated ...
    (freebsd-current)
  • Re: Log Out Issues
    ... UDP is the way to go for internet games. ... Apparently the extra overhead in TCP can cause a lot more lag in your game, ... >> Lets say the client sends a log out request to the server reliably. ...
    (microsoft.public.win32.programmer.networks)
  • Re: Log Out Issues
    ... your perormance may be worse than TCP. ... would be if your protocol anticipates packet loss and does not ... >>> Lets say the client sends a log out request to the server reliably. ...
    (microsoft.public.win32.programmer.networks)
  • Re: [2.6.24.3][net] bug: TCP 3rd handshake abnormal timeouts
    ... server via TCP and non-persistent connections and all application level ... "Sometimes" when establishing a TCP connection to the server, ... Here is a simplified version of what _both_ the server and the client ...
    (Linux-Kernel)