|
midrange.com
Thanks Chuck,
I have configure TCP/IP for 2 previous system emulating other systems or
following IBM recommendation but your response put AS/400 TCP/IP in some
perspective. My current system can not be seen from my PC (client) but can
be "pinged" I'm curious if the TCP/IP on the AS/400 is configured wrongly.
I used Windows explorer to find the AS/400 using IP and IP name but to no
success.
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
----- Original Message -----
From: "Chuck Morehead" <cbmorehead@nokuse.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, January 02, 2002 11:14 AM
Subject: Re: TCP/IP and Components
> <snip>
> > First: What are the functions of ROUTES, *DFTROUTE, NEXTHOP, and
> PREFERRED INTERFACE and why are they needed.
> Different subnets don't normally "talk" to each other. If you want them
to,
> then you need to tell them how to get to each other, i.e. what "route" to
> take. E.g. to get from a machine with IP 10.1.1.15 (assuming mask of
> 255.255.255.0) to subnet 10.1.2.0, you need to tell the 10.1.1.15 system
> where the router is, e.g. perhaps it is 10.1.2.1. This tells the
10.1.1.15
> machine to go to 10.1.2.1 for any 10.1.2.0 address.
>
> The *DFTROUTE option is the default route - it is tried if there are no
> specific routes that meet the request. It is the same as a "default
> gateway" in Windows.
>
> >
> > Second: How should TCP/IP domain be setup and what are the
relationship
> and requirements between HOST NAME, DOMAIN NAME, DOMAIN
> > NAME ADDRESSES as they apply to AS/400 TCP/IP domain.
> This is a matter of opinion, and is very arbitrary if you are working with
> an internal network. E.g. use "yourcompanyname.com" for the domain name,
> and your AS/400's name for the host name. E.g. here our domain is
> NOKUSE.COM. (In our situation we use the same domain as our public
domain,
> which does not cause us problems since we do not host our own Internet
> servers in-house. If you do have Internet servers in-house then you may
> want a different domain name for internal systems. Again, this is very
> arbitrary.) Then if our AS/400's host name was AS400 the qualified name
> would be AS400.NOKUSE.COM.
>
> As for IP address, choose a private IP scheme, e.g. 192.168.20.0 or
> 10.1.1.0. Generally servers (i.e. anything that requires a static IP) use
> the first 10 (or more if you need them) IP's. So your router may be
> 10.1.1.1, your AS/400 may be 10.1.1.2, you may have 3 print servers using
> 10.1.1.3-5, etc. This allows you to set your DHCP server (if you choose
to
> use one) to exclude that range.
>
> > Third: What are the functions of a *LOOPBACK address.
> Loopback is for testing TCP/IP locally to make sure you at least have
TCP/IP
> up and running. It does not test outside the machine you are working on.
> >
> <snip>
>
> There is a lot more to all of this, but basic configuration on the AS/400
is
> easy. Configuring and securing it - especially if your network is
connected
> to the Internet - is another animal.
>
> Chuck
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
