Re: Changing ports used by TCP/IP servers

Vern,

You can probably just configure the LinkSys to forward from the
non-standard port to the standard port.  In other words, block ports 21 and
23 at the LinkSys and have it forward 10021 and 10023 to the FTP and Telnet
ports.

I am pretty sure, however, that the port scanners that hackers use are
smart enough to find these openings.

Mark



      To:   midrange-l@midrange.com
      cc:
      bcc:
      Subject:    Changing ports used by TCP/IP servers
vhamberg@attbi.com
Sent by: midrange-l-admin@midrange.com
07/26/2002 11:29 PM GMT
Please respond to midrange-l        <font size=-1></font>





















I want to change the port used by telnet. I saw the
postings on the archive that say to call qtcp/qtgsrv
after changing the services table. Can this be done back
in v3r7? Was there a PTF back that far?

In the same vein, can something like this be done for
ftp - or does ftp take the service table changes without
intervention? I did not do a search on this.

There seems to be a problem, though, with the standard
Windows client, which does not seem to have a port
argument for ftp. Maybe clients like Cute & WS-FTP do
better?

The reason for doing this is, we have 3 machines, 2
behind a LinkSys DSL/cable gateway (router), 1 out in
front, naked to the world. I want to put all 3 behind
the LinkSys, and then assign non-standard ports for
telnet and ftp on the 3 boxes. Then I'll make the
LinkSys forward traffic to each box according to port.
(We'll get VPN someday, I hope, soon!) We do have a need
for customers to upload data, as well as for us to
connect to these boxes remotely.

Thanks

Vern
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.