Timothy,
you didn't mention, which client OS you're using.
In general, I think ADSM makes use of the standard TCP/IP sockets
implementation of the OS. On NT, for example, it's the WINSOCK
implementation.
Any machine that initiates a session has to do this on a predefined port
(like 1500), when a session gets established, another port has to be used to
get the original one fre for other connections.
The ports for this already initiated connection are selected randomly on
both sides, using API functions of the Sockets implementation. These
functions have access to a list of ports already in use and return a free
and usable one.

I don't think it will be a feature in ADSM to restrict the usage of ports to
a small range, but it could be possible to trick the Sockets API functions
in a way, so they believe only a small range of port numbers to be
available...
Therefor you could browse thru the helpfiles of your network package.

Good luck,
regards
Michael
--
Michael H. Bartl
Michael H. Bartl
ADAC e.V. (Rechenzentrum, Produktionsplanung und Organisation)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de

> ----------
> Von:  Gaverth, Timothy, J. Mr. (Tim)
> (GSFC-255.7)[SMTP:Timothy.J.Gaverth.1 AT GSFC.NASA DOT GOV]
> Gesendet:     Mittwoch, 30. September 1998 10:58
> An:   ADSM-L AT VM.MARIST DOT EDU
> Betreff:      force client tcp port
>
> Okay, I've browsed the archives, I've looked in all documentation I have,
> and I can't find my own answer to this:
> How can I force the server to talk to a client on a specific port? I know
> about 1500, 1501, and 1580 on the server, and that's fine. But, I need to
> use one port, or a few (but pre-determined) ports, on the client. Do I
> give
> the client a dsmc listener, and if so, how?
> Thanks for any help.
>
> Timothy J. Gaverth
> Systems Administrator
> NASA/GSFC - BATCS
> (301)286-9282(voice);(301)286-1619(fax)
> tim.gaverth AT gsfc.nasa DOT gov
>