Bug 14782

Summary:	ypbind can not bind to Solaris NIS master server
Product:	Base System	Reporter:	bauer <bauer>
Component:	bin	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description bauer 1999-11-08 07:20:00 UTC

There is a Solaris7 running as NIS master server.
1) in rc.conf the YP client is set to YES but ypbind does not start on 
system boot.
2) maual start of ypbind does not give any error but it does not bind
to the server: "ypwhich: can't yp_bind: reason: Domain not bound"
It is the same if I start it with full command line specification of
NIS domain and server in the -S option.
3) Tried to use ypset
ypbind -ypset
ypset -h mp -d gp astro
- after 1 min it returns with this timeout error:
ypset: can't yp_bind, reason: Can't communicate with ypbind
The ypbind is running:
mp# ps -ax | grep yp
 5607  ??  Is     0:00.01 ypbind -ypset
 5621  ??  S      0:00.00 ypbind -ypset

Comment 1 Tony Maher 1999-11-14 22:23:47 UTC

>      There is a Solaris7 running as NIS master server.
>      1) in rc.conf the YP client is set to YES but ypbind does not start on
>      system boot.

I run a similar setup and it works fine (solaris 7 - FreeBSD
3.3-stable).
Have you set nisdomainname in /etc/rc.conf (NB it is case sensitive)??

Comment 2 bit-bucket 2000-02-24 02:34:07 UTC

I have the same problem, ypbind will not bind to my solaris-7
yp server.

nisdomainname is set in rc.conf.
`domainname` reports the proper domain name.

ypwhich reports the proper machine to be bound to even though
ypbind is not running!

ypcat and other utilities act normally; i.e. not bound.

ypbind forks and exits silently.  Unfortunately, truss doesn't
follow the fork, so I can't tell what's going on. ktrace
doesn't work on ypbind.

    -- Brad	

-- 
   -- Brad Lanam      bll@gentoo.com

Comment 3 Tony Maher 2000-02-26 09:16:55 UTC

As indicated previously I have not had any trouble on the local LAN in
the
office in getting NIS to bind to a Solaris 7 server (from FreeBSD
3.4-stable).

Just tried from home over modem and I do get problems in binding.
THere were 2 copies of ypbind and they were repeatedly dying and 
spawning new copies.

tcpdump showed that broadcasts going over home ethernet network rather
than
over tun0 interface.

20:02:16.680190 dt.1217 > 192.168.0.255.sunrpc: udp 132

From the man page

ypbind -m -S nis.int.DOMAIN,foo.int.domain,bar.int.domain

fixed the problem for me.

I am wondering if you are in a subnet and your broadcasts are not
reaching the NIS master.

tonym

Comment 4 bit-bucket 2000-02-26 21:37:48 UTC

    This problem is an issue with the /etc/rc.network
    script and in other configuration scripts somewhere.
    Something in the configuration/installation process set
    'network_interfaces' in /etc/rc.conf to "tx0 auto".

    The /etc/rc.network script will not process this 
    correctly, as the "auto" value is only expanded at
    the top level, not within the loop that processes
    network interfaces.

    This means that the loopback (lo0) interface never
    comes up, and all sorts of rpc stuff will fail to
    work.

    -- Brad

-- 
   -- Brad Lanam      bll@gentoo.com

Comment 5 Mike Barcroft freebsd_committer

2001-07-21 03:48:41 UTC

State Changed
From-To: open->feedback


Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE?

Comment 6 Matt Jacob freebsd_committer

2001-10-02 04:58:02 UTC

State Changed
From-To: feedback->closed

I bind to Solaris 7 and Solaris 8 NIS masters fine, and this PR has 
been in feedback state for a long time. Closed.