Date: Sun, 15 Nov 1998 17:45:42 -0500 (EST) From: Bill Paul <wpaul@skynet.ctr.columbia.edu> To: yuri@xpert.com Cc: bugs@FreeBSD.ORG Subject: Re: bin/8699: ypbind can't bind to server Message-ID: <199811152245.RAA06478@skynet.ctr.columbia.edu> In-Reply-To: <199811152151.NAA06135@hub.freebsd.org> from "yuri@xpert.com" at Nov 15, 98 01:51:00 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Of all the gin joints in all the towns in all the world, yuri@xpert.com had to walk into mine and say: > > >Number: 8699 > >Category: bin > >Synopsis: ypbind can't bind to server > >Confidential: no > >Severity: serious > >Priority: high > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sun Nov 15 14:00:01 PST 1998 > >Last-Modified: > >Originator: Yuri Gindin > >Organization: > >Release: 3.0-RELASE > >Environment: > FreeBSD moon.moon.com 3.0-RELEASE FreeBSD 3.0-RELEASE #0: Sat Nov 14 19:13:12 IST 1998 root@moon.moon.com:/export/home/src/sys/compile/MOON i386 > >Description: > ypbind can't bind to the server running Solaris-2.6 > From the other hand, when running ypbind -s -ypsetme > and then ypset servername > one can get the following message after timeout for about 15 sec: > /usr/sbin/ypset: sorry, cannot ypset for domain domainname on host > But then, yp works. > >How-To-Repeat: > ypbind -s -S domainname,servername > ypwhich > ypwhich: can't yp_bind: reason: Domain not bound > > >Fix: > > >Audit-Trail: > >Unformatted: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > > This is one of those problems that's hard to track down unless you're actually there to look at the configuration. Murphy's Law says there's a very simple configuration problem at work here, not a software bug, but since I can't actually see your system I can't even guess what the problem might be. I doubt that Sun has changed their ypserv implementation and I know I haven't changed FreeBSD's ypserv. Of course, you could be using rpc.nisd in compat mode on the server, but we'll never know because you decided not to share this useful piece of information. You also didn't say if your server is a Solaris 2.6 x86 or SPARC system. Until I can duplicate your problem, _you_ need to sit down and do some debugging. Go to the Solaris machine, become root and run 'snoop' or tcpdump and watch the traffic between the Solaris and FreeBSD host. This will probably give you some idea what's wrong. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811152245.RAA06478>