NIS-server refuses connects from clients

Hello,

I replaced an old server by a new one can't get NIS working again. At the
clients I just altered the IP of the server, so they should be OK. Here is
exactly what happens:

client:

<screen>
r4:~ ypbind -debug
parsing config file
Trying entry: ypserver 192.168.0.6
add_server() domain: winux, host: 192.168.0.6, slot: 0
[Welcoms to ypbind-mt, version 1.41]

ping host ´192.168.0.6´, domain ´winux´
Pinging all active server.
</screen>

the last two line are repeated about once per minute or so.

At the server I get the following entry for every ping from the client
in /var/log/messages:

<messages>
.... ypserv[pid]: refused connect from 192.168.0.4:32770 to procedure
ypproc_domain_nonack (winux, ;0)
</messages>

How can I figure out why the connect is refused?

Here my configuration:

Client (SuSE 9.0)

<defaultdomain>
winux
</defaultdomain>

<yp.conf>
ypserver 192.168.0.6
</yp.server>

Server (SuSE 10.0)

<defaultdomain>
winux
</defaultdomain>

<yp.conf>
ypserver localhost
</yp.conf>

<ypserv.conf>
dns: no
files: 30
slp: no
xfr_check_port: no
* : * : shadow.byname : port
* : * : passwd.adjunct.byname : port
</ypserv.conf>

Thanks, Dieter

Dieter Gardeike wrote:

> ...
> <log>
> ... ypserv[pid]: refused connect from 192.168.0.4:32770 to procedure
> ypproc_domain_nonack (winux, ;0)
> </log>
> ...

Ouch!

Stop the server with

r6:~> rcypserv stop

Restart it with debug output

r6:~> ypserv -d

And I got (now directly to the console):

ypproc_domain_nonack("winux") [From: 192.168.0.4:32770]
refused connect from 192.168.0.4
-> Ignored (forbidden by securenets)

And a close look at /var/yp/securenets revealed transposed digits :-o.

Dieter