|
Boy, This is a very scary statement. I would suggest that you think very long and hard about putting a valid public IP address directly on your AS/400 IF it is running any mission critical applications. Rather I recommend to my customers that they use a private IP address (RFC-1918) for there AS/400 and map the connections they wish people to have from the Internet to the AS/400 through a FireWall. Don't map FTP or Telnet if all you want is a SSL Web server connection. The use of NAT (Network Address Translation) in a Firewall product also allows you to close and restrict access to the system, as well as develop your Intranet independently from the ISP you choose today. If today use MCI and tomorrow you use IBM all that would change on your network is the NAT map in the Firewall, and the secondary DNS resolution for Intranet/internet name. Lastly, watch the VPN issues closely. if you want to use encryption and encapsulation over the Internet then Firewalls give you more options as to rather the user/site has access your intranet or a specific system on your Intranet. This field and technology is changing rapidly, and I support all three technologies as a means of establishing a connection for the user, you just need to carefully way the budget, reliability, throughput, and security issues in making your choice. BUT always start with the door closed, and open it as appropriate. Jeff Silberberg.. -----Original Message----- From: boothm@ibm.net <boothm@ibm.net> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> Date: Thursday, March 11, 1999 9:02 PM Subject: Re: Connecting satellite locations via the Internet >Once the AS/400 has a true internet ip address then any of the outlying shops, or even salesmen's hotel rooms, can use AOL, ibm.net, or whoever they usually use and just click their copy of Client Access and they have a sign-on screen from anywhere. There's no magic, it just happens. The remote support effort is almost nothing, and remote printing becomes trivial. It really is that simple, once the AS/400 is on-line. > > >In <36E8155F.44E0@postoffice.worldnet.att.net>, on 03/11/99 > at 11:11 AM, Pat Barber <MBOCEANSIDE@postoffice.worldnet.att.net> said: > >>I would prefer to hear about a "small" remote location and how you go >>about connecting them to a 400.. (small means 2-4 users)... I am very up >>on all the "normal" methods...Web access is the only thing I would like >>to hear about.. > >-- >----------------------------------------------------------- >boothm@ibm.net >Booth Martin >----------------------------------------------------------- > >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@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 >+--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.