Re: How to make my iSeries at home available to outside programmers

Hmm, I'm getting a question---what if you want to allow access to 2
servers, both with the same protocol(s)? If you have NAT, you don't give
them your internal address, do you? I mean, those are often blocked out in
the big bad Internet, I believe.

And you don't have the luxury of setting up gateways (routes) based on
destination and subnet, as we do on the 400.

This is similar to something I'm trying to do at work. (Yes, we have to do
it more securely - someday!) But I have an iSeries with a public address
(mask of 255.255.255.248 from our ISP) that is our development box. This
subnet is connected to our intranet with a LinkSys router. All developers
are behind the NAT function of this router. I've set up forwarding for port
4200 (STRCODE's default) to my PC. Will I muck things up by having
additional entries on the same port but to different machines? I have a
route on the 400 for 192.168.0.0 mask 255.255.255.0 with next hop being the
side of the router that is on the same subnet as the 400. BTW, the default
route for the 400 goes through the DSL modem.

I suspect we really need a more robust, flexible firewall/proxy/NAT to do
what we want (I show some of my ignorance there <g>).

At 05:17 PM 7/16/02 -0500, you wrote:


>On Tue, 16 Jul 2002, Richard wrote:
> >
> > At home I have a small network of PC's all connected and sharing a
> > single cable modem.
> > I have purchased an iSeries Model 270 running V5R1 and I have managed to
> > connect it to my home Network.
> > Now I would like to make my iSeries available to several programmers who
> > work out of their homes.
> >
> > My question is - What is the easiest way for me to give access to my
> > iSeries to people outside of my home network?
>
>There's nothing iSeries-specific about the network setup.  You allow
>people to access your iSeries in exactly the same way that you'd allow
>someone to access your PC from the Internet.   The only real difference
>is that the iSeries is designed to work with terminals, so you won't be
>as limited in what you can do once you've connected.
>
>The steps I'd follow would be:
>
>      1) Find out if you have a static IP, or if you can get one for
>           a reasonable price.   For any serious work, you're going to
>           want a static IP.  (that means that your ISP doesn't ever
>           assign you a different IP, you always have the same one)
>
>      2) If you don't want or can't afford a static IP, set your LAN
>           up with a dynamic dns service.  This would allow you to use
>           DNS to look up your current IP, even if it has changed.
>           One such service that I know of is www.dyndns.org, but there
>           are thousands of them out there...
>
>      3) You didn't mention how your LAN works...  but since you have
>           multiple machines that are able to access the internet, you
>           must either have   (1) multiple IP addresses being routed
>           properly, (2) a NAT ("ip masquerading") server set up, or
>           (3) some sort of proxy services.   Whichever method you use,
>           you'll need to configure it to route incoming connections
>           to your iSeries.
>
>      4) Your iSeries will need to be configured for TCP/IP and will
>           need the appropriate servers turned on.  (i.e. telnet, ftp,
>           web... whatever services you plan to offer)
>
>Once you've done that, people would be able to use a Telnet (or Telnet
>5250 "TN5250") client to connect to your iSeries.   That would be very
>easy.