Stream socket client/server connection problems

Article View: comp.unix.programmer

Article #24

Back to comp.unix.programmer Previous Next

#24

From: Rob Cash
Date: Thu, 29 Oct 1992 20:13

64 lines
2913 bytes

Hello, everyone.

I have a question for you concerning establishing stream socket connections
without using a reserved port from the /etc/services file.  Basically, the
question is: how can the client determine the server's port, if the server's
port was assigned automatically by the operating system because s_port was 0?

Any ideas?
Wizards, if this question was too trivial for your group, then I apologize
for the waste your bandwidth.

Please send replies to rmcash@eos.ncsu.edu.


Thanks in advance,

Rob

--
Robert M Cash                                  NN   NN  TTTTTTTT  LL
Northern Telecom, Ltd.                         NNN  NN     TT     LL
35 Davis Dr.                                   NNNN NN     TT     LL
RTP, NC 27709                                  NN NNNN     TT     LL
USA                                            NN  NNN     TT     LL
(919) 991-8243                                 NN   NN     TT     LLLLLLL

#include <std_disclaimer>

Path: brtph21!rmcash
Newsgroups: comp.unix.programmer, comp.unix.wizards
Distribution: world
From: rmcash@brtph21.bnr.ca (Rob Cash)
Reply-To: rmcash@eos.ncsu.edu (Rob Cash)
Organization: Bell Northern Research, RTP, NC
Subject: Stream socket client/server connection problems
Keywords: socket, client/server, /etc/services

Hello, everyone.

I have a question for you concerning establishing stream socket connections
without using a reserved port from the /etc/services file.  Basically, the
question is: how can the client determine the server's port, if the server's
port was assigned automatically by the operating system because s_port was 0?

Any ideas?
Wizards, if this question was too trivial for your group, then I apologize
for the waste your bandwidth.

Please send replies to rmcash@eos.ncsu.edu.


Thanks in advance,

Rob

--
Robert M Cash                                  NN   NN  TTTTTTTT  LL
Northern Telecom, Ltd.                         NNN  NN     TT     LL
35 Davis Dr.                                   NNNN NN     TT     LL
RTP, NC 27709                                  NN NNNN     TT     LL
USA                                            NN  NNN     TT     LL
(919) 991-8243                                 NN   NN     TT     LLLLLLL

#include <std_disclaimer>

Technical Details

Message-ID: <1992Oct29.201303.16217@brtph560.bnr.ca>

Path:

arc1-ca.pugleaf.net!sparky!uunet!charon.amdahl.com!pacbell.com!ames!sun-barr!cs.utexas.edu!news.uta.edu!hermes.chpc.utexas.edu!news.utdallas.edu!corpgate!brtph560!brtph21!rmcash

Show Full Headers

Complete Article Headers

Newsgroups: comp.unix.programmer,comp.unix.wizards
Path: arc1-ca.pugleaf.net!sparky!uunet!charon.amdahl.com!pacbell.com!ames!sun-barr!cs.utexas.edu!news.uta.edu!hermes.chpc.utexas.edu!news.utdallas.edu!corpgate!brtph560!brtph21!rmcash
From: rmcash@brtph21.bnr.ca (Rob Cash)
Subject: Stream socket client/server connection problems
Message-ID: <1992Oct29.201303.16217@brtph560.bnr.ca>
Keywords: socket, client/server, /etc/services
Sender: news@brtph560.bnr.ca (Usenet News)
Reply-To: rmcash@eos.ncsu.edu (Rob Cash)
Organization: Bell Northern Research, RTP, NC
Date: Thu, 29 Oct 1992 20:13:03 GMT
Lines: 67