Thanks all!
It works! It turned out to be a firewall issue as most of you had
predicted. After I had the network administrator add the rule, it went
through fine.
Thanks again for everyone's help!
/b;
-----Original Message-----
From: Scott Klement [
mailto:midrange-l@xxxxxxxxxxxxxxxx]
Sent: Tuesday, April 24, 2007 2:15 PM
To: Midrange Systems Technical Discussion
Subject: Re: Setting up i5 for External Access
Hello,
TRACEROUTE RMTSYS(NRA.ORG)
Probing possible routes to NRA.ORG (64.29.201.96) using *ANY
interface.
1 192.168.0.141 2.75 2.54 2.63
2 * * *
3 * * *
4 * * *
[SNIP]
Probing possible routes to NRA.ORG (64.29.201.96) using *ANY
interface.
1 192.168.0.2 0.512 0.544 0.448
2 192.168.0.141 2.66 2.54 2.57
3 *
It would appear that 192.168.0.141 is a firewall that's blocking certain
types of traffic. Perhaps it's blocking UDP on the traceroute ports?
Or perhaps it's blocking ICMP? Both of these things are common, and
both would provide the same result.
Tools like TRACEROUTE and PING are useful inside your own corporate
network where you know what is and isn't blocked. But, once you go out
to the Internet, people start blocking a lot of things to protect
against DOS attacks, and this makes it very difficult to use them for
diagnostics.
I'd suggest trying a TCP connection to a well-known port. Much less
likely to be blocked than UDP or ICMP.
On the bright side, your 192.168.0.2 hop (L3 switch, I guess) appears to
be routing traffic for you. So you know that the L3 switch and i5/OS
are set up properly. The issue seems to primarily be with the
192.168.0.141 host, which I'm guessing is a firewall, and I'm guessing
that it's not configured to let you through.
midrange.com
