From mi@misha.cisco.com  Thu Feb 11 07:57:37 1999
Received: from misha.cisco.com (misha.cisco.com [171.69.206.50])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05654
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 11 Feb 1999 07:57:36 -0800 (PST)
          (envelope-from mi@misha.cisco.com)
Received: (from mi@localhost)
	by misha.cisco.com (8.9.1/8.9.1) id KAA17750;
	Thu, 11 Feb 1999 10:53:23 -0500 (EST)
	(envelope-from mi)
Message-Id: <199902111553.KAA17750@misha.cisco.com>
Date: Thu, 11 Feb 1999 10:53:23 -0500 (EST)
From: Mikhail Teterin <mi@misha.cisco.com>
Reply-To: mi@aldan.algebra.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: ypxfr does not work with Solaris master server(s)
X-Send-Pr-Version: 3.2

>Number:         10031
>Category:       bin
>Synopsis:       ypxfr does not work with Solaris master server(s)
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 11 08:00:01 PST 1999
>Closed-Date:    Thu Jul 19 19:17:49 PDT 2001
>Last-Modified:  Thu Jul 19 19:28:12 PDT 2001
>Originator:     Mikhail Teterin
>Release:        FreeBSD 3.0-RELEASE i386
>Organization:
Virtual Estates, Inc.
>Environment:

	The master server nis1, apparently, redirects requests to another
	(slave?) server nis2. Both of them run Solaris.

>Description:

	Local, FreeBSD-3.0-RELEASE machine tries to

	ypxfr -p /var/yp -h nis1 -c -d mydomain

	I put debug messages into ypxfr, which is why it is a bit more
	verbose here:

	ypxfr: couldn't create udp handle to ypserv: RPC: Program not registered
	ypxfr: source was: nis2		<-- my message on ypxfr_misc.c:229
	ypxfr: failed to get order number of passwd.byname from nis2:
		RPC failure talking to server	<-- my modifiction of message
						    on ypxfr_main.c:368

>How-To-Repeat:

	See the setup above

>Fix:

	I think, this has to do with ypxfr not failing over properly to
	the SunOS compatable strategy, but I'm not sure... I wish, there
	was a switch to not even try the FreeBSD-specific algorithm...	
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Thu Jul 19 16:13:25 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=10031 
State-Changed-From-To: feedback->closed 
State-Changed-By: mike 
State-Changed-When: Thu Jul 19 19:17:49 PDT 2001 
State-Changed-Why:  

The originator indicated to me, in a private e-mail, that he is 
unable to test whether this has been resolved in a newer release. 

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