RE: Grumble...

["Neil Palmer" <neilp@xxxxxxxxxxx>]

Joe,

First, try ending and restarting TCP/IP services.
You don't mention which OS/400 release and PTF cum package level your 400 
is at, but there are PTF's to fix situations where TCP traffic can stop on 
the 400.  (You say you assume you see two ARP packets from the 400 - maybe 
they aren't ?).

Play with comm trace on the 400.  STRCMNTRC, ENDCMNTRC, PRTCMNTRC (FMTTCP 
*YES) while attempting to ping out and connect in from the outside (one 
test only per each run of comm trace to keep it easy).

Here's a REAL long shot - could your AS/400's MTU size (on the TCP/IP 
interface definition, or the Ethernet line description) be set to a value 
too large for your Netopia router ?  If you try to connect to the 400 from 
the outside, does the sniffer show data going to the 400 ?

Neil Palmer 






"Joe Pluta" <joepluta@PlutaBrothers.com>
Sent by: owner-midrange-l@midrange.com
2001/02/25 23:47
Please respond to MIDRANGE-L

 
        To:     <MIDRANGE-L@midrange.com>
        cc: 
        Subject:        RE: Grumble...


Final piece to the puzzle.  When I put up a sniffer, the AS/400 doesn't 
even
make a peep on the network during the ping.  When I ping internally, I see
two ARP broadcast packets from what I assume is my AS/400, followed by a
response from what I assume is my router.  After that, there are a bunch 
of
ICMP echos and replies.  When I ping an unconfigured address in the net,
there are a whole bunch of ARP broadcasts, but of course no replies.  And
when I ping an address NOT in the subnet, there isn't even a peep on the
ether - not even an ARP broadcast.

So how about THEM apples, eh?


> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Joe Pluta
> Sent: Sunday, February 25, 2001 9:57 PM
> To: MIDRANGE-L@midrange.com
> Subject: RE: Grumble...
>
>
> And just to clarify - the AS/400 successfully pings 10.1.1.17
> (the internal
> address of the router).  The AS/400 can in fact ping ANY of the
> machines on
> the internal network.  It simply cannot ping anything past the
> router.  All
> other machines on the network, however, can indeed ping inside and 
outside
> the network (including pinging the AS/400).
>
> The AS/400 cannot even ping the realworld address of the router.  All 
the
> other machines do, with under 10msec response time (on the other hand,
> pinging a realworld address other than the router is on the order of 100
> msec).  It seems to me that the AS/400 is simply not sending out
> any packets
> to addresses other than itself.  Now to grab a sniffer and see if
> that helps
> anything.
>
> Joe
>
>
> > -----Original Message-----
> > From: owner-midrange-l@midrange.com
> > [mailto:owner-midrange-l@midrange.com]On Behalf Of Alex A Moore
> > Sent: Sunday, February 25, 2001 7:58 PM
> > To: MIDRANGE-L@midrange.com
> > Subject: RE: Grumble...
> >
> >
> > Joe,
> >
> >              Your 10.1.1.* address needs a router or firewall or some
> > means of being
> > "routed" or "natted" to an external public address.  Normally ( is 
there
> > such a thing ) you would have all of your private addresses inside of 
a
> > firewall.  Your firewall might translate, via NAT, your 10.
> > private address
> > to an external and public address.  Your router may also perform this
> > function.
> >
> > Do you know how to run a comm trace on your AS/400?  Do you have
> > one of the
> > downloadable TRACERT utilities for the AS/400?  Is your one and
> only route
> > active?  A process called dead gateway processing will make your route
> > inactive for a period of time if your next hop cannot be pinged by the
> > AS/400.
> >
> > Alex
> >
> > -----Original Message-----
> > From: owner-midrange-l@midrange.com
> > [mailto:owner-midrange-l@midrange.com]On Behalf Of Joe Pluta
> > Sent: Sunday, February 25, 2001 5:50 PM
> > To: MIDRANGE-L@midrange.com
> > Subject: Grumble...
> >
> >
> > Can't get my AS/400 to do any webserving.  All my machines have 
private
> > addresses and we all talk together wonderfully.  My NT machine
> and my W2K
> > machine can ping out just fine.  My AS/400 cannot.  I checked my 
routing
> > table, and I have only one entry, my *DFTROUTE, which points to
> my router:
> >
> >
> >       Route            Subnet           Next             Preferred
> >  Opt  Destination      Mask             Hop              Interface
> >       *DFTROUTE        *NONE            10.1.1.17        *NONE
> >
> > Looks good to me.  But when I try to ping a real world address, I get
> > unsuccessful attempts.  The only thing I can think of is to try
> and use my
> > router's REALWORLD IP address.  I'll try that next.
> >
> > Joe


+---
| 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
+---