ypbind of 10.20 client failing

[David Anderson]

Hi,

I have just installed a couple of 10.20 hosts with the latest Support +
updates.

However ypbind (with no command line options) is unable to bind to the
domain that I have setup. Two other machines on the network segment
(linux and HP-UX 11-00) are able to bind no problems.

Has anyone experienced this at all and/or could suggest a solution.

I have changed the config so that ypbind is called with -ypset and then
the command ypset is run with the domain and ypserver arguments, however
this is unsuitable in the long term.

Thanks

David Anderson

[Matt Alderson]

I dont understand what you are trying to do, ie "unable to bind
to the domain that I have setup". You say other machines can bind
without a problem so I assume the ypserv is running on ANOTHER
machine, right? All you need do is set the correct params in
the file /etc/rc.config.d/namesvrs :
NIS_CLIENT="1"
NIS_DOMAIN="whatever_you_call_it"
reboot

Have you tried typing "domainname" ? I am betting it is not set.
It must be in order for ypbind to work with no options.
David Anderson <drm_an...@hotmail.com> writes:

--
Matt Alderson GIS Specialist . Arizona Game and Fish Department
email: mald...@gf.state.az.us . 2221 W. Greenway Road
voice-mail: (602) 789-3610 . Phoenix, AZ 85023 U.S.A.

[Chuck Slivkoff]

David Anderson wrote:
>
> I have just installed a couple of 10.20 hosts with the latest Support +
> updates.
>
> However ypbind (with no command line options) is unable to bind to the
> domain that I have setup. Two other machines on the network segment
> (linux and HP-UX 11-00) are able to bind no problems.
>
> Has anyone experienced this at all and/or could suggest a solution.
>
> I have changed the config so that ypbind is called with -ypset and then
> the command ypset is run with the domain and ypserver arguments, however
> this is unsuitable in the long term.

ypbind will broadcast for a server. Verify your IP/mask. If there isn't
a server w/in the same subnet, you will need to use ypset.

[David Anderson]

The ypserver is on 172.16.1.1 and the clients are on 172.17.1.x
There are 5 clients in total: 3 10.20, 1 11.0 and a linux box. All have
the same netmask and are 172.17.1.x addressed.
The 11.0 and linux box bind to the NIS domain without any problems.

On the 10.20 clients the namesvrs file does have the correct settings as
you suggested

NIS_CLIENT="1"
NIS_DOMAIN="whatever_you_call_it"

when I run the ypwhich I get
NIS domain "whatever" is not bound, and when I type domainname I do get
back "whatever"
When I set the ypbind option to -ypset and then run ypset -d "whatever"
172.16.1.1 the 10.20 clients bind sucessfully

I don't understand what is happening when I think I have set up NIS
correctly.

David

Matt Alderson wrote:
>
> I dont understand what you are trying to do, ie "unable to bind
> to the domain that I have setup". You say other machines can bind
> without a problem so I assume the ypserv is running on ANOTHER
> machine, right? All you need do is set the correct params in
> the file /etc/rc.config.d/namesvrs :
> NIS_CLIENT="1"
> NIS_DOMAIN="whatever_you_call_it"
> reboot
>
> Have you tried typing "domainname" ? I am betting it is not set.
> It must be in order for ypbind to work with no options.
> David Anderson <drm_an...@hotmail.com> writes:
>
> > Hi,
> >

> > I have just installed a couple of 10.20 hosts with the latest Support +
> > updates.
> >
> > However ypbind (with no command line options) is unable to bind to the
> > domain that I have setup. Two other machines on the network segment
> > (linux and HP-UX 11-00) are able to bind no problems.
> >
> > Has anyone experienced this at all and/or could suggest a solution.
> >
> > I have changed the config so that ypbind is called with -ypset and then
> > the command ypset is run with the domain and ypserver arguments, however
> > this is unsuitable in the long term.
> >

[Christian Haug]

David Anderson wrote:
>
> Hi,
>
> I have just installed a couple of 10.20 hosts with the latest Support +
> updates.
>
> However ypbind (with no command line options) is unable to bind to the
> domain that I have setup. Two other machines on the network segment
> (linux and HP-UX 11-00) are able to bind no problems.
>
> Has anyone experienced this at all and/or could suggest a solution.
>
> I have changed the config so that ypbind is called with -ypset and then
> the command ypset is run with the domain and ypserver arguments, however
> this is unsuitable in the long term.
>
> Thanks
>
> David Anderson

Hello,

remember to set your yp-server in the file /var/yp/secureservers.
Perhaps you forgot this.

Christian
-------------------------------------------------------
E-Mail: ha...@uni-freiburg.de

[David Anderson]

The problem was stupid really and should have been solved in 30 minutes
by myself if I had _just looked_ more closely!

So I own up and apologise - wild goose chase is over.

The hp-ux 11 has the following two lines set in
/etc/rc.config.d/namesvrs which the 10.20 hosts did not.

YPBIND_OPTIONS="-ypset"
YPSET_ADDR="server_name"

Upon adding these settings to the 10.20 hosts all worked like a dream.
I had assumed that the hp-ux 11.0 machine had managed to get round the
netmask/broadcast issue - it had but I could not see how.

The linux box has a similar entry in a file in /etc as well.

Sorry for the wild goose chase.

David Anderson