Here we do it by allowing port 1500 through, and then established TCP
connections.
Most firewalls know how to do this.  This way you only need to allow port 1500.

At 11:18 AM 12/11/97 -0500, you wrote:
>Be carefull with this. You need to know how ip sockets work. By default, the
>server socket number is 1500, and the clients' is 1501. But this is only
for the
>original connection to the target machine. That is, these are listening ports
>only. Let's just look at the client connecting to the server.
>
>When the client tries to connect to the server, it will connect to the servers'
>port 1500, but it will select a random port number for its outgoing call (say,
>973). This port is assigned by the tcp/ip software running on the client. Once
>connected, the server will fork another process with its own port number to
>continue conversing with the client. If this didn't happen, then only one
client
>would ever be able to open a session with the server at any given time.
>
>Clear as mud?
>
>
>
>
>
>
>From: John Groves <jmg AT OPENMIC DOT COM> on 11/30/97 04:27 PM GMT
>
>Please respond to jmg AT openmic DOT com
>
>To:   ADSM-L AT VM.MARIST DOT EDU
>cc:    (bcc: ADSM)
>Subject:  What TCP Port does ADSM use?
>
>
>
>
>We need to enable certain remote client connections to an ADSM server
>through a firewall.  Does anybody know what port(s) must be enabled to
>allow ADSM clients to connect to the server?
>Thanks,
>John Groves
>jmg AT openmic DOT com
>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> Tim Dobrowolsky                   > <                yksloworboD miT <
> Computer Services                 > <              secivreS retupmoC <
> Catonsville Community College     > <  egelloC ytinummoC ellivsnotaC <
> tim AT catrs.cat.cc.md DOT us            > <         su.dm.cc.tac.srtac@mit <
> 410-455-4562                      > <                   2654-554-014 <
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<