RE: Changing ports used by TCP/IP servers

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

If you can get to just one as400 via telnet, you can then telnet from that
system 5250 job to the other as400's.  At a command line type telnet (system
name or ip address)


-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@attbi.com]
Sent: Friday, July 26, 2002 10:27 PM
To: midrange-l@midrange.com
Subject: Re: Changing ports used by TCP/IP servers


Thanks, John, I'll look at these things.

I agree, having everything in triplicate is daunting. I think there'll be
only 1 that'll be opened up for ftp - this'd be for customer uploads, esp.,
plus our own work remotely. Then we'd get on the system ourselves and ftp
internally, as needed, so there's really no NEED for different ports here.

telnet on different ports isn't so bad, since we mostly use this for PC5250
or other emulation, and those have the capability to set ports, so that's a
one-time thing. The same for our products, in which you set up the ports
yourself anyway. The other one that matters to me now is the Websphere Dev
Studio client stuff - again, you set these up once and then don't need to
enter them every time.