SCOUG-Programming Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Thu, 1 Oct 1998 21:20:00 PDT
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com
Subject:	SCOUG-Programming: FTP server - ports

Content Type: text/plain

You know, I'm reading my own post and even _I_ can't understand it.

Peter Skye wrote:
>
> How do you block ports from being assigned?
> (and a bunch of mumbo jumbo afterwards)

I'll try again.

If we start the FTP server, it listens at some preassigned port. If a
user logs in, they're given a different port on which to conduct
business.

Where do we list ports that we don't want the FTP (or other) server to
assign to a user? My specific reason is that I might have some "other"
server which only runs occasionally, and this "other" server listens at
some preassigned (but different) port just like the FTP server. I don't
want the FTP server to ever assign that particular port to a user, so
that it's always available in case I start my "other" server.

Example: My "other" server listens at port 2300, but I haven't started
it yet. The FTP server sees a user log on and (through TCP/IP, I guess)
assigns a unique port to that user. If port 2300 is, by chance,
assigned to the FTP user, then I can't start my "other" server.

- Peter Skye

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 01 | October | 1998 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.