From nobody@FreeBSD.ORG Sun Nov  7 23:19:58 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 63D2215151; Sun,  7 Nov 1999 23:19:58 -0800 (PST)
Message-Id: <19991108071958.63D2215151@hub.freebsd.org>
Date: Sun,  7 Nov 1999 23:19:58 -0800 (PST)
From: bauer@genprofile.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: ypbind can not bind to Solaris NIS master server
X-Send-Pr-Version: www-1.0

>Number:         14782
>Category:       bin
>Synopsis:       ypbind can not bind to Solaris NIS master server
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov  7 23:20:00 PST 1999
>Closed-Date:    Mon Oct 1 20:58:02 PDT 2001
>Last-Modified:  Mon Oct 01 20:58:38 PDT 2001
>Originator:     David Bauer
>Release:        3.2
>Organization:
GenProfile AG
>Environment:
FreeBSD mp 3.2-RELEASE FreeBSD 3.2-RELEASE #0: Wed Sep 22 08:59:38 GMT 1999     root@mp:/usr/src/sys/compile/MP  i386

>Description:
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

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:

From: Tony Maher <tony.maher@eBioinformatics.com>
To: freebsd-gnats-submit@freebsd.org, bauer@genprofile.com
Cc:  
Subject: Re: bin/14782: ypbind can not bind to Solaris NIS master server
Date: Mon, 15 Nov 1999 09:23:47 +1100

 >      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)??
 

From: Brad Lanam <bit-bucket@gentoo.com>
To: freebsd-gnats-submit@FreeBSD.org, bauer@genprofile.com
Cc:  
Subject: Re: bin/14782: ypbind can not bind to Solaris NIS master server
Date: Wed, 23 Feb 2000 18:34:07 -0800

 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
 

From: Tony Maher <tony.maher@eBioinformatics.com>
To: freebsd-gnats-submit@FreeBSD.org, bauer@genprofile.com,
	bll@gentoo.com
Cc:  
Subject: Re: bin/14782: ypbind can not bind to Solaris NIS master server
Date: Sat, 26 Feb 2000 20:16:55 +1100

 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
 

From: Brad Lanam <bit-bucket@gentoo.com>
To: freebsd-gnats-submit@FreeBSD.org, mjacob@feral.com,
	tony.maher@eBioinformatics.com, bauer@genprofile.com
Cc:  
Subject: Re: bin/14782: ypbind can not bind to Solaris NIS master server
Date: Sat, 26 Feb 2000 13:37:48 -0800

     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
 
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Fri Jul 20 19:48:41 PDT 2001 
State-Changed-Why:  

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

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14782 
State-Changed-From-To: feedback->closed 
State-Changed-By: mjacob 
State-Changed-When: Mon Oct 1 20:58:02 PDT 2001 
State-Changed-Why:  
I bind to Solaris 7 and Solaris 8 NIS masters fine, and this PR has 
been in feedback state for a long time. Closed. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14782 
>Unformatted:
