Alexander Goldberg wrote:
> run 'nisdomain' on client machine
>
> make sure you're using the same nisdomain as ypserver uses
> Att! It's not nessesary your real domain, you mai call it "BLAH"
> for example.
>
> also check that on client machine you have
>
> domain 'YOUR NISDOMAIN NAME' server 'YO
>
> So , if you really need client to broadcast download
> ypbind 3.3< , compile it , and enjoy.
Let me understand , you're telling there was broadcast feature in ypbind < 3.3
and now it's thrown away? Why then it tries to send broadcasts over the network?
Elya
=
Why not ?
from "NIS-Howto"
-
Old ypbind versions do a broadcast to find a running NIS server. This
is insecure, due the fact that anyone may install a NIS server and
answer the broadcast queries. Newer Versions of ypbind (ypbind-3.3 or
ypbind-mt) are a
yp.conf:
domain compugen.co.il broadcast
The problem is ypbind cannot communicate with ypserverduring the startup
, and it's definitely Linux ypbind
problem since other platforms do it well.
Thanks anyway
Elya
[EMAIL PROTECTED]
=
To u
run 'nisdomain' on client machine
make sure you're using the same nisdomain as ypserver uses
Att! It's not nessesary your real domain, you mai call it "BLAH"
for example.
also check that on client machine you have
domain 'YOUR NISDOMAIN NAME' server 'YOUR_YPSERVER_IP'
Hello!
I'm using Suse 6.2. I am trying to transfer ypclient to broadcast mode
unsuccessfully
( ypset works Ok, other platforms work Ok in broadcast mode )
When running "ypbind -broadcast -debug" , I get:
broadcasting for domain compugen.co.il
broadcast: RPC: Timed out.
There are 3 ypbin
