NIS+ problem....

[HPP]

Hi,
1) I initialize NIS+ on HP-UX 11.00. After initialization SAM does not work properly. SAM sits at initial window saying "Initializing SAM....), it does not go any further.
2) So i wanted revert back from NIS+, what i did is changed "/etc/rc.config.d/namesvrs" file to not start NIS+ at boot time and rebooted the server. Now SAM comes up fine, but it take lot and lot of time to come up.

/etc/nsswitch.conf has an entry "hosts: files[NOTFOUND=continue] dns" after initializing NIS+ and after stoping NIS+.
/etc/resolv.conf is fine, as i am able to do nslookup and browse the web.

Any solution for the 1st and 2nd senario.....

Thanks in advance....

[Craig Rants]

Ok, a few tests

hostname

nslookup ip address

nslookup hostname

Also, what is the contents of your resolv.conf, do you have domain yourdomain.com, search manydomains.com?

First make sure the three commands produce the desired results.

Let us know,
C

[HPP]

Craig Rants,
thanks for the response.
I ran
1. nslookup myhostname
it came out with rigth IP Address
2. nslookup
it came out with the right server name.
3. resolv.conf contians
domain abc.com
nameserver xx.xx.xx.xx

[Sanjay_6]

Hi,

check the patch level on your system. You probably need the sam/obam patch on your system.

This is the latest sam/obam patch. also look for other patches.

http://us-support3.external.hp.com/wpsl/bin/doc.pl/screen=wpslDisplayPatch/sid=9d05e7d313c517fd9a?PACH_NAM=PHCO_23876&HW=s800&OS=11.00

Hope this helps.

Regds

[Craig Rants · Accepted solution]

Generally, SAM is a little slow when it runs into some networking issues, namely it can't determine who it is in a reasonable amount of time. Since you have your nsswitch.conf file listed with files first, try putting a entry in /etc/hosts which will tell the server who he is. Use a short name and the FQDN as well in the entry. Also once SAM does come up look in the SAM log for any errors.

The path to that is SAM -> Options -> View Sam log...

See if that changes anything.

[HPP]

Guys,
Thanks for quick response.
It was problem with the host file. IP address was not correct.

Thanks again.....