Re: AS/400 as a web server -- MIDRANGE-L

To get inbound SMTP to work, you set up a 'service' on port 25.  Bind it to
both cards (inside and outside).  Set up a default mapping (on the Mapping
tab) to the IP address of your AS/400 on the inside.  This will cause all
SMTP traffic showing up on the 'outside' card to get forwarded to your
AS400.  Set up another mapping on the 'Location' tab.  This mapping should
say that any port 25 traffic coming from the IP address of your AS400 should
be forwarded to the ip address or FQDN of your ISP's SMTP relay.  Tell the
AS400 that your Wingate box is your SMTP Gateway (i.e. don't expect the
AS/400 to deliver straight to the destination domain).  This part was a
bear - you can't put your Wingate IP address in here - you need a routing
table entry (I think...).  If you can't get this part to work, email me
privately and I'll backtrack and figure out how the heck I got this working.

Set up your domain's MX record to be the outside IP address of your Wingate
box (hopefully you have a fixed IP address).  Bingo.... mail coming to your
domain will forward to the AS400's SMTP server.  SMTP coming from the AS400
to the internet will go to the Wingate box as a 'relay', which will then
automatically relay it to your ISP's relay, who will then deliver it.

Good luck.  Let me know if I can help any more.

----- Original Message -----
From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, March 24, 2000 2:33 PM
Subject: RE: AS/400 as a web server


> I'd be interested in hearing what settings in wingate you needed to make
to
> allow SMTP to work on the AS/400.  :)  Been fighting with it for some time
> now.
>
> Brad
>
> -----Original Message-----
> From: David Shea [mailto:dshea@arctools.com]
> Sent: Friday, March 24, 2000 10:24 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: AS/400 as a web server
>
>
> I've had good luck with Wingate proxy software.  It was a bear to get
> running the first time, and it only took me about a year to get the vendor
> to admit that it doesn't really work that great on a 95 box.  It works
> flawlessly on an NT Workstation box, or an NT Server box.  This is a
'little
> PC, two NICs' scenario.
>
> I've gotten it to work fine with an AS400, even being able to do all the
> Client Access Express features, CODE/400, client/server, etc from the
> outside.  SMTP, etc, all OK.  It wasn't easy, though.  Lots of tinkering.
> But then most firewalls will be a challenge.
>
> Wingate's in-house support is weak, and they don't know how to even spell
> AS400, but the thing works once you figure out how to configure it.
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Time share a current model AS/400 over the internet!
> Individual developers, company development and testing, or full
outsourcing.
> Get access to RPG, Cobol, C, SQL, Java and more for a low monthly fee.
> http://www.timeshare400.com
> mailto:timeshare400@arctools.com
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ----- Original Message -----
> From: <mcrump@ballfoster.com>
> To: <MIDRANGE-L@midrange.com>
> Sent: Friday, March 24, 2000 9:17 AM
> Subject: Re: AS/400 as a web server
>
>
> >
> >
> > >> I'm no expert by any stretch in the area of firewalls but we like
what
> we
> > >>hear
> > >> other people are saying about the CISCO PIX 520...........all flames
> will
> > >>be
> > >> ignored since I am ignorant.....
> >
> > >400 people are so anti-PC.
> >
> > Anti-PC?  Naw.  I live and die by them.  Our existing firewall is based
on
> > a little PC.  It has been unstable, has a few holes, and absolutely
> > can't handle VPN.  So we made a mistake.  Not necessarily the
> > fault of a PC based firewall.
> >
> > I personally want a firewall that's supported and integrates into our
> > future router environment (CISCO).  I'll probably take a look
> > at your ideas but at a starting price of $5,000 the PIX doesn't seem
> > to be an expensive solution.
> >
> > >Purchase a little PC.  Put two NICs in it.  It doesn't even need a
> full-time
> > >monitor or keyboard.
> > >Install OpenBSD.  Its focus is security.  It's free.
> > >http://www.openbsd.org/
> > >Learn ipf (IP Filter).  Stateful firewall software.  Again, free.
> > >http://www.obfuscation.org/ipf/
> > >Build a deny-by-default ipf ruleset.
> > >Bing.
> > >
> > >It will take time and a lot of reading, but it's an excellent and cheap
> > >solution.
> >
> >
> >
> >
> > Michael Crump
> > Ball-Foster Glass Container Co.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > +---
> > | 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
> +---
> +---
> | 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
+---