Re: NIS problem

"Jim Christiansen" <christiansen_j@xxxxxxxxxxx> · Thu, 20 Nov 2003 07:56:08 -0700

Hello Steven,

The docs that I read stated that the NISDOMAIN=name is different from
the host name.  So I went with it and kept them different.

The configs that I sent are the only ones I have that have worked, so far...

Jim

In yp.conf of your working system (NIS client) you have a line
domain linux-thin1.blablabla.bla server 192.168.1.175
while in the /etc/sysconfig/network of linux-thin1.blablabla.bla is
NISDOMAIN=linux-thin
I think domain should be the NISDOMAIN, not the server name.  I.e.,
assuming 192.168.1.175 is an IP number of linux-thin1.blablabla.bla,
domain linux-thin server 192.168.1.175
But maybe if you have the correct domain in your working system's
/etc/sysconfig/network, that takes care of the domain name, and you can
just have in /etc/yp.conf of your NIS client
ypserver 192.168.1.175

On Wed, 19 Nov 2003, Jim Christiansen wrote:

>From my working system:

Here is my yp.conf-
# /etc/yp.conf - ypbind configuration file
# Valid entries are
#
#domain NISDOMAIN server HOSTNAME
#       Use server HOSTNAME for the domain NISDOMAIN.
#
#domain NISDOMAIN broadcast
#       Use  broadcast  on  the local net for domain NISDOMAIN
#
#ypserver HOSTNAME
#       Use server HOSTNAME for the  local  domain.  The
#       IP-address of server must be listed in /etc/hosts.
#
domain linux-thin1.blablabla.bla server 192.168.1.175
ypserver 192.168.1.175

and

[root@linux-thin1 root]# cat /etc/ypserv.conf

#

# ypserv.conf   In this file you can set certain options for the NIS 
server,

#               and you can deny or restrict access to certain maps based

#               on the originating host.

#

#               See ypserv.conf(5) for a description of the syntax.

#

# Some options for ypserv. This things are all not needed, if
# you have a Linux net.

# Should we do DNS lookups for hosts not found in the hosts table ?
# This option is ignored in the moment.
dns: no

# How many map file handles should be cached ?
files: 30

# xfr requests are only allowed from ports < 1024
xfr_check_port: yes

# The following, when uncommented,  will give you shadow like passwords.
# Note that it will not work if you have slave NIS servers in your
# network that do not run the same server as you.

# Host                     : Domain  : Map              : Security
#
*                        : *       : passwd.byname    : port
*                        : *       : passwd.byuid     : port

# Not everybody should see the shadow passwords, not secure, since
# under MSDOG everbody is root and can access ports < 1024 !!!
#                          : *       : shadow.byname    : port
#                          : *       : passwd.adjunct.byname : port

# If you comment out the next rule, ypserv and rpc.ypxfrd will
# look for YP_SECURE and YP_AUTHDES in the maps. This will make
# the security check a little bit slower, but you only have to
# change the keys on the master server, not the configuration files
# on each NIS server.
# If you have maps with YP_SECURE or YP_AUTHDES, you should create
# a rule for them above, that's much faster.
# *                        : *       : *                : none

AND
[root@linux-thin1 root]# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=linux-thin1.blablabla.bla

NISDOMAIN=linux-thin

Hope this helps,

Jim

_________________________________________________________________

Add photos to your e-mail with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=features/photos&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca

--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list