Re: Setting up i5 for External Access

[Pete Helgren <Pete@xxxxxxxxxx>]

Brain,

The DNS server is internal so it can resolve the domain to an IP, so 
that makes sense.  Did your tracert make it out of your local network?  
You said it went out through the firewall device.  How far did it get?

Pete (butting in...sorry)

Brian Piotrowski wrote:
> Hi Rob,
>
> I am able to ping internally with no issue (I get a response back from
> all internal devices).  When I ping an external site, I do not receive a
> response.  However, it does return the IP address of the site I am
> pinging (i.e.: NRA.ORG returns 64.29.201.96).
>
> So it appears that IP resolution works, but ping doesn't.  When I did a
> tracert from my desktop, it doesn't go through our L3 switch, but
> instead through the firewall device.  I went and changed the default
> route on the i5 from our L3 switch to the firewall device and tried
> another ping.  Still no dice.  It will show me the IP address, but the
> ping fails.
>
> Any ideas?
>
> Thanks!
>
> /b;
>
>
> -----Original Message-----
> From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] 
> Sent: Tuesday, April 24, 2007 11:50 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: Setting up i5 for External Access
>
> Start with the basics.
> http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzaku/rzakut
> oolsvfy.htm
> Find an ip address that your i5 should be able to ping internally.
> Let's 
> make sure that internal works before testing external.
> >From an i5 command line type in
> PING 'xxx.xxx.xxx.xxx' 
> where the x's are the ip address of something internal.  You'll need the
>
> apostrophes.
> A fantastic example of something that your i5 should be able to ping by
> ip 
> number is the DNS.
>
> If that works then try something externally.  Try 64.29.201.96.  They 
> return pings.  If that site is down, I grab my gun and head for the
> woods.
>
> If you can ping that site by IP number try pinging it by name.
> PING NRA.ORG
>
> Keep us posted...
>
> Rob Berendt
>