Okay, if you can ping your AS/400 from your PC, or
vice versa, then they can "see" each other.

Lets see, your AS/400 has 2 IPs, 10.160.9.59 and
10.160.9.66.  Your subnet mask is 255.255.255.0 so
this means that your AS/400 should be able to "see"
directly (without using gateway) any other machine
in your network with 10.160.9.xxx

Your PC is using DHCP so it could be getting any
address, I'm assuming your DHCP is set to serve the
10.160.9.xxx subment.

Can you, from your PC, PING 10.160.9.66 ?  If you
can, then you can see your AS/400 on your local
network.

How your 2 default routes are going to work is
beyond me, although the default route should not
come to play when talking on your local network
(10.160.9.xxx).

*DFTROUTE   *NONE        10.160.9.254    10.160.9.59
*DFTROUTE   *NONE         162.6.61.1       162.6.61.8

I believe you probably want to put a subnet mask on the
second one, your TRNLINE71, but if it's working now, I
wouldn't mess with it as I could be wrong on that.

In short, if you can ping your AS/400 from your PC, and/or
your PC from your AS/400 (run the DOS command IPCONFIG on
your PC to find it's current IP address) then they can
see each other.  Then it's just a matter of setting up the
software.

---------------------------------

Short note on IP addresses, local networks, subnet masks
and default gateways.

Any machine that has an IP address should also have a
subnet mask.  It conbines these two to determine which
IP's it can talk to directly (are on the local network)
and which it has to use the gateway for (Wide Area Network).

Your local subnet seems to be set up as 10.160.9.xx with
a subnet mask of 255.255.255.0.  Any IPs a machine in your
local network try to contact with 10.160.9 they will try
to talk to directly.  If they can't find them directly,
they give up.   Any IP address outside of that range they
will ask the Default Router to get for them.

The Loopback IP address (usually defined 127.0.0.1) is
an IP address that means this machine.  When you connect
to 127.0.0.1 or loopback you are talking to your own
machine.  It is sometimes called Localhost.

HTH,

Regards,

Jim Langston

From: "Dare" <oludare@ix.netcom.com>

<SNIP>
The following are my PC IP configuration:
DNS Servers:    10.248.0.30
Node Type:        Hybrid
IP Address:        DHCP
Subnet Mask:     255.255.254.0
Default Gateway:    10.160.2.254
DHCP Server:    10.160.3.6
Primary Wins      10.160.10.37
Secondary Wins  10.160.9.37
_________________________________
The following are my AS/400 IP configuration:

Internet         Subnet                     Line                   Line
Address          Mask                     Description        Type
10.160.9.59    255.255.255.0      ENETLIN01     *ELAN
10.160.9.66    255.255.255.0      ENETLIN02     *ELAN
127.0.0.1        255.255.255.128  *LOOPBACK  *NONE
162.6.61.8      255.255.255.128  TRNLINE71     *TRLAN
_________________________________
Route                Subnet           Next                 Preferred
 Destination        Mask             Hop                  Interface
*DFTROUTE   *NONE        10.160.9.254    10.160.9.59
*DFTROUTE   *NONE         162.6.61.1       162.6.61.8
_________________________________
                        Change TCP/IP Domain (CHGTCPDMN)
 Type choices, press Enter.

 Host name  . . . . . . . . . . .   'sys400'
 Domain name  . . . . . . . . . .   'company.org'
 Host name search priority  . . .   *REMOTE       *REMOTE, *LOCAL, *SAME
 Domain name server:
   Internet address . . . . . . .   '162.6.5.5'
                                            '162.6.6.2'
                                            '10.248.0.30'
                            Additional Parameters
   Port . . . . . . . . . . . . . .   53            1-65535, *SAME
 Protocol . . . . . . . . . . . .   *UDP          *UDP, *TCP, *SAME
_________________________________
                       Change TCP/IP Attributes (CHGTCPA)
 Type choices, press Enter.

 TCP keep alive . . . . . . . . .   120           1-40320, *SAME, *DFT
 TCP urgent pointer . . . . . . .   *BSD          *SAME, *BSD, *RFC
 TCP receive buffer size  . . . .   16384         512-8388608, *SAME, *DFT
 TCP send buffer size . . . . . .   16384         512-8388608, *SAME, *DFT
 UDP checksum . . . . . . . . . .   *YES          *SAME, *YES, *NO
 Path MTU discovery:
   Enablement . . . . . . . . . .   *YES          *SAME, *DFT, *NO, *YES
   Interval . . . . . . . . . . .   10            5-40320, *ONCE
 IP datagram forwarding . . . . .   *YES          *SAME, *YES, *NO
 IP source routing  . . . . . . .   *YES          *SAME, *YES, *NO
 IP reassembly time-out . . . . .   120           5-120, *SAME, *DFT
 IP time to live  . . . . . . . .   64            1-255, *SAME, *DFT
 ARP cache timeout  . . . . . . .   5             1-1440, *SAME, *DFT
 Log protocol errors  . . . . . .   *YES          *SAME, *YES, *NO


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.