RE: Ping returning wrong address

Hoss:

>From the information I have read on this parm, the zero is an internal
versioning mechanism that may be for future use. The Lotus Yellowbooks for
system administration list the entry syntax as:

[TCPIP-PORTNAME]_TcpIpAddress=0,[TCPIP-ADDRESS]:[PORT-NUMBER]

They offer no explanation of the zero or any other values that position may
have.

---------------------
Kevin E. Mort
iSeries Technical Support
Support Net, Inc.
Ph: 888.480.TECH
Fx: 954.428.3991
Mailto:kmort@supnet.com

IBM Certified Expert - e(logo)server iSeries 400 Technology
Lotus Certified Specialist

" i want everything to work. i choose iSeries. "


<SNIP>

Subject: RE: Ping returning wrong address
Date: Thu, 29 Nov 2001 13:34:51 -0600
From: "Bruce Collins" <bacollins@twitchellcorp.com>
To: <midrange-l@midrange.com>
Reply-To: midrange-l@midrange.com

Kevin, what is the 0 for before the IP address.

Hoss

-----Original Message-----
From: KMort@supnet.com [mailto:KMort@supnet.com]
Sent: Thursday, November 29, 2001 1:02 PM
To: midrange-l@midrange.com
Subject: Re: Ping returning wrong address



It would be a good practice to always set the name server search to
*LOCAL
from CHGTCPDMN. This will always hit the 400 host table first before
going
out to a remote name server. This could also be an issue however, if you
have an entry in the host table AND one on DNS...you would need to
update
both locations if something changes.

It is also recommended that besides making sure you specify the TCP
address
specifically (which I would think you have done by saying that each
server
has its own address) in the notes.ini file - for example:

TCPIP_TcpIpAddress=0,10.23.224.170:1352

Lastly it is further recommended that you do have host table entries not
only for the fully qualified name of the 400 but also the Domino
servers.

This avoids confusion if your remote DNS servers may not have totally
updated with new info or you have a cache issue. For internal system
communications, the host table is better than a remote server. In fact
certain parts of MGTC may fail simply due to the fully qualified name of
the 400 not being in that host table.

</SNIP>