Yes...you need to be sure that both forward and reverse lookup are
fuctioning.  Name resolution is ultra-sensitive!

-----Original Message-----
From: Discussion of IBM NetView and POLYCENTER Manager on NetView
[mailto:NV-L AT UCSBVM.UCSB DOT EDU]On Behalf Of Gord Michaels
Sent: Wednesday, June 09, 1999 10:22 AM
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: Re: Managed node creation failed!


Hello All.

I have discovered something which may be the problem...

On the client I want to make my managed node, I cannot do(i.e cannot find
it) a:

nslookup server_IP

But I can do a nslookup server_hostname

Also, on the TMR server side...

I cannot do(i.e. cannot find it) a: nslookup client_IP

But I can do a: nslookup client_hostname

Could this be my problem ???

Gord.



>From: "Ken Garst." <KGarst AT GIANTOFMARYLAND DOT COM>
>Reply-To: Discussion of IBM NetView and POLYCENTER Manager on NetView
>        <NV-L AT UCSBVM.ucsb DOT edu>
>To: NV-L AT UCSBVM.ucsb DOT edu
>Subject: Re: Managed node creation failed!
>Date: Wed, 9 Jun 1999 09:43:12 -0400
>
>You didn't mention if you are using DNS or flat file /etc/hosts for name
>resolution.  I am using /etc/hosts for name resolution and had exactly the
>same
>problem in creating a managed node for a NetView client.  After much
>investigation, the solution is to "fake" out Tivoli by copying the
>/usr/bin/nslookup command to, say, nslookup.ORIG and then create a fake
>nslookup
>file containing the following commands:
>
>echo "Name: <hostname of TMR server.domain.name>"
>echo "Address: <ipaddr of TMR server"
>
>In my particular case, the fake nslookup file contains:
>
>echo "Name:  nvhost.hq.giantofmaryland.com"
>echo "Address:  161.247.21.237"
>
>After the install, copy back the original file to the nslookup file.
>
>Regards,
>ken
>kgarst AT giantofmaryland DOT com
>


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com