Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!rice!sun-spots-request
From: david@eng.sun.com
Newsgroups: comp.sys.sun
Subject: Re: ypset not allowed?
Keywords: Networks
Message-ID: <6678@brazos.Rice.edu>
Date: 13 Apr 90 19:15:13 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n110
X-Sun-Spots-Digest: Volume 9, Issue 123, message 1

In article <6626@brazos.Rice.edu> gnb@melba.oz.au (Gregory N. Bond) writes:
|X-Sun-Spots-Digest: Volume 9, Issue 110, message 14
|
|We have just updated to SunOs 4.0.3, and have come across some problems
|with YP.  I presume it has to do with the increased security of YP in this
|release.  I have not installed the "Security" install stuff, so we don't
|use authenticated RPC etc etc.  Our YP master is a 3.5 machine.
|
|When I try to run ypset (which we need to do, as clients have a habit of
|binding to machines on the other end of a MAC bridge, overloading the link
|in the middle), I get an error message:
|
|  Sorry, I couldn't send my rpc message to ypbind on host wran.

"Documented in 4.1"

In order to be able to do a ypset from any machine you need to start
ypbind with the -ypset option.  If you only need to be able to ypset on
the machine itself use -ypsetme instead.

David DiGiacomo, Sun Microsystems, Mt. View, CA  david@eng.sun.com