RE: Sockets problem (what is)

Actually, in a "normal" client/server environment, such as Telnet, the
client *doesn't* switch ports.

The server will have a listener on some port.  In this case telnet port 23.
A client requests a connection to the server on port 23.  The server
receives the request and hands the port off to a new thread (usually) which
establishes the connection on some other port.  As far as the client is
concerned you are connected on the server on port 23, although in the server
it may see it is port 5123.  The client doesn't know, or care, what the real
port is on the server.  That port switching is all server side and the
client doesn't see it or even know if it's happening.

Regards,

Jim Langston

-----Original Message-----
From: Ron@cpumms.com [mailto:Ron@cpumms.com]

Jim,
We're not actually sending/receiving those messages, at least I don't think
we are. That was psuedo code from Buck describing the procsess that we
needed to follow. After the initial connection is made, the server moves us
to another port and we don't know how to determine what port we were moved
to.

Ron Hawkins