Re: Connecting an AS400 to the Internet

[Carl Galgano <cgalgano@xxxxxxxxxxxxxxxxx>]

Vernon makes some great points (as usual).  We alos have visibility to the
Internet bout from our internal network and to our AS400 from the Internet
via local ISP and we can use developers from all around the world.  We have
only a single IP address assigned to the internet.  The IP address is
configured to a proxy server that acts as our primary gate to the internet.
 All outbound traffic to the Internet has the same IP address regardless of
which device on the internal network makes the request.  Out proxy server
only allows access to specific ports of specific machines on the internal
network.  Therefore we can limit AS400 access from the internet to only
Telnet.  But still allow services like FTP to our internal users or users
who dial our internal network via our RAS server.  It was really quite easy
to set up.  As far as speed, in order to test this out. we initially have
established a dedicated 33.6 dial account with an ISP that will assign a
static IP address.  The cost is minimal (75/month) and the response is
good.  I suspect we will move to ISDN or some other connectivity at some
point in time, however, we usually get sub second response over the
internet. Green screen apps that only write data in blocks of about 2000
characters per screen do not tax a 33.6 line.  Heck, I have worked for some
companies that have run remote facilities (20 users) on 9.6 leased lines
using SDLC.  IP is much more efficieint and response times are much better
using IP rather than SNA over the same connection speed.
Carl

At 11:30 AM 5/14/98 -0500, you wrote:
>John
>
>At 08:21 AM 5/14/1998 -0700, you wrote:
>>I am looking at hooking an AS400 to the internet so that programmers can
>use it. I would like some input as to how and what I would need to do this.
>>
>>I do not have the AS400 yet, thinking of a model 170. How many programmers
>could the base 170 handle? What would I need on the AS400? What type and
>speed of modem or will something on network handle this (I do not have the
>network ether) ? I would like to start off with ISDN 64K, then go to ISDN
>128K, then whatever is next if need be. Or should I start with something
>else? Does anyone know how many programmers could work on each one of these
>lines without to bad a response (I would like sub second, if possible). In
>the future (two years)  may need to tie more then one AS400 together. Would
>like PC’s from the same location as the AS400 to have access to the
>internet.  Need to allow the programmers to upload/download source, files
>(data)  objects (if that is possible) and to print, all of this to PC’s and
>AS400’s (at other locations, over the internet).  What will need to be on
>the programmers PC, other AS400? Will a normal dial up access be fast
>enough? How secure is all of thi!
>>s going to be? Now for the all important question, cost, one time and
>monthly fees?  Since the monthly cost will have to be passed along to the
>programmers please keep that in mind when making recommendations ( I do not
>know how many programmers I will be starting with, lets say 1 to 10). Also
>I am not a network person, so not to technical.
>
>I don't have all answers to everything you've asked. However, let me tell
>you a little of what we have set up.
>
>We have multiple PCs on an Ethernet network (you only need to install the
>cards in the PCs and connect with appropriate cable). We happen to have
>Novell Netware, but I don't think you need that to provide the Internet
>access. All you need is the physical connection, and IP addresses for each
PC.
>
>Our development 400 is also on that same Ethernet network.
>
>We have a router on the Ethernet network that connects with a 56K frame
>relay line (with appropriate CSU/DSU—something like a modem but for high
>speed) to an Internet service provider. I think this is probably the
>easiest way to get going. You can get a class C block of IP addresses
>(about 254) for your use, from the ISP. The ISP will give you DNS addresses
>to use. The line's speed can be increased over time.
>
>Security is a problem here, because any of these addresses you assign
>internally are visible to the big, bad, Internet. You need a router that
>can do some kind of packet filtering, at the least. Your ISP should be able
>to help here, too. True firewalls/proxy/SOCKS servers are better but more
>complex. The basic premise is to block all traffic, then open your net up
>to known, trusted sources.
>
>With this kind of setup, our internal users have access to the Internet.
>And someone like me can get to the 400, e.g., by connecting with my own
>ISP. All I need is the address of the 400. Client Access' PC5250 emulation
>uses telnet protocol, so it's a natural for this. This emulation is one of
>the licensed portions of Client Access, so Graphical Access may be good
>enough. And FTP makes for great file transfer. The main problem is the
>non-standard format of the 400's FTP directory info. Things like Cute FTP
>can't handle it.
>
>If you need file & print sharing, you might want to use NT Server or Novell
>or Lantastic. BTW, you already have network printing to AS/400 printers
>with Client Access.
>
>================================
>
>Another possibility is dialup to some kind of multiple connection modem.
>This modem would feed a single ASYNC line on the 400. The 400 can make SLIP
>connections this way, and maybe PPP by now on v4r2. Speed is listed (v4r1)
>at 19200, but you can probably use faster.
>
>This has the advantage of giving you a reasonable expectation of privacy,
>since it is dialup and not as public as anything over the Internet.
>
>But this approach does not address internal users who need to get access to
>the Internet. I believe you can have the 400 dial out to an ISP, but I'm
>not sure of that.
>
>Hope this helps a little
>
>Vernon Hamberg
>Systems Software Programmer
>Old Republic National Title Insurance Company
>400 Second Avenue South
>Minneapolis, MN  55401-2499
>(612) 371-1111 x480
>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator: david@midrange.com
>+---
>
Carl J. Galgano
http://cgalgano.home.mindspring.com
mailto:cgalgano@ediconsulting.com
EDI Consulting Services, Inc.   
540 Powder Springs Street
Suite C19
Marietta, GA 30064
770-422-2995
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---