[95974] in RedHat Linux List
Re: YPBINDPROC_DOMAIN: Domain not bound
daemon@ATHENA.MIT.EDU (Chris J. Manders)
Thu Oct 22 15:08:00 1998
Date: Thu, 22 Oct 1998 12:06:42 -0700 (PDT)
From: "Chris J. Manders" <cmanders@mh1.lbl.gov>
Reply-To: "Chris J. Manders" <cmanders@mh1.lbl.gov>
To: redhat-list@redhat.com
Resent-From: redhat-list@redhat.com
Hi,
I will deal with your first issue:
If you have a NIS server, then you need to join the NIS domain with the command domainname.
Of course, if you have no networking at all then it will not be able to bind to the
server....so fixing the latter problem will likely fix the former one.
--Chris
> Gentlemen,
>
> I am running RedHat Linux 5.1 with kernel 2.0.35 on a Pentium 233 MMX
> computer, which is equipped with 64 Megs of RAM, 4 Gig Wide SCSI hard
> disk, Realtek 8029 PCI Ethernet card, etc.
>
> I set up a local home network with a 486 25 MHz computer with 32 Megs
> of RAM, 1 Gig SCSI 2 hard disk, NE2000 ISA Ethernet card, running
> RedHat Linux 4.2 with kernel 2.0.29. I have been trying to setup NFS/NIS
> following the docs on the RedHat Linux CDROMs. I have set all the
> hostnames, domainnames, ypdomainnames and IP addresses as best I can.
> However, I am having a problem with the 486 25 MHz computer not being
> able to ping or telnet to the Pentium 233 MHz computer. The ping error
> that I am getting is 198.168.110.0 not responding and when I try to
> telnet, I get a "protocol not found" error message on the 486 25 MHz
> computer. Then on the Pentium 233 MHz computer I am receiving the
> following email about every 5 - 10 minutes:
>
> >From root Wed Oct 21 15:01:01 1998
> Return-Path: <root>
> Received: (from root@localhost)
> by pentium233.pc.com (8.8.7/8.8.7) id PAA00676
> for root; Wed, 21 Oct 1998 15:01:01 -0400
> Date: Wed, 21 Oct 1998 15:01:01 -0400
> Message-Id: <199810211901.PAA00676@pentium233.pc.com>
> From: root@pentium233.pc.com (Cron Daemon)
> To: root@pentium233.pc.com
> Subject: Cron <root@pentium233> run-parts /etc/cron.hourly
> X-Cron-Env: <SHELL=/bin/bash>
> X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
> X-Cron-Env: <MAILTO=root>
> X-Cron-Env: <HOME=/root>
> X-Cron-Env: <LOGNAME=root>
> Status: R
>
> YPBINDPROC_DOMAIN: Domain not bound
> YPBINDPROC_DOMAIN: Domain not bound
>
> First, I would like to know what is causing the "YPBINDPROC_DOMAIN: Domain
> not bound" error message on the Pentium 233 MHz computer and how to fix
> it?
>
> Second, I would like to know what could be wrong with the 486 25 MHz
> computer not being able to communicate with the Pentium 233 MHz computer
> on the 10base2 network. I know the NE2000 ISA card works because I can
> boot up Novell DOS 7 with Personal NetWare and transfer files with the
> Pentium 233 MHz computer without a problem. I have the I/O Address and
> the IRQ number set correct in the conf.modules file in the /etc directory
> in RedHat Linux 4.2 and Linux finds the card and loads the ne2000 module
> driver without any errors.
>
> The I/O Address and the IRQ number of the ne nic via /etc/conf.modules
> are as follows:
>
> alias eth0 ne
> options ne io=0x300 irq=10
>
> The following is the ifconfig.eth0 file in /etc/sysconfig/network-scripts
> directory:
>
> DEVICE="eth0"
> IPADDR="198.168.110.25"
> NETMASK="255.255.255.0"
> NETWORK=198.168.110.0
> BROADCAST=198.168.110.255
> ONBOOT="yes"
> BOOTPROTO="none"
> USERCTL=no
>
> The following is the ifconfig.lo file in /etc/sysconfig/network-scripts
> directory:
>
> DEVICE=lo
> IPADDR=127.0.0.1
> NETMASK=255.0.0.0
> NETWORK=127.0.0.0
> BROADCAST=127.255.255.255
> ONBOOT=yes
> BOOTPROTO=none
>
> The following is the network file in /etc/sysconfig directory:
>
> NETWORKING=yes
> FORWARD_IPV4=no
> HOSTNAME="smith486-25.pc.com"
> DOMAINNAME=smith486-25
> GATEWAY=
> GATEWAYDEV=
> IPX="yes"
> IPXINTERNALNETNUM="1"
> IPXINTERNALNODENUM="1"
> IPXAUTOPRIMARY="off"
> IPXAUTOFRAME="off"
> NISDOMAIN="smith486-25.com"
>
> On the 486 25 MHz computer, Linux is set up to work with this network as
> follows:
>
> # ifconfig
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
> RX packets:371 errors:0 dropped:0 overruns:0
> TX packets:371 errors:0 dropped:0 overruns:0
>
> eth0 Link encap:Ethernet HWaddr 00:30:2b:01:1c:54
> inet addr:198.168.110.25 Bcast:198.168.110.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0
> TX packets:39 errors:0 dropped:0 overruns:0
> Interrupt:10 Base address:0x300
>
> # route -n
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 198.168.110.0 0.0.0.0 255.255.255.0 U 0 0 3 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 2 lo
>
> The following is the exports file in /etc directory:
>
> / pentium233.pc.com(rw)
>
> The following is the HOSTNAME file in /etc directory:
>
> smith486-25.pc.com
>
> The following is the host.conf file in /etc directory:
>
> order hosts nis bind
> multi on
>
> The following is the hosts file in /etc directory:
>
> 127.0.0.1 localhost localhost.localdomain
> 198.168.110.2 smith486-25.pc.com smith486-25.pc
> 198.168.110.1 pentium233.pc.com pentium233.pc
>
> The following is the hosts.allow file in /etc directory:
>
> #
> # hosts.allow This file describes the names of the hosts which are
> # allowed to use the local INET services, as decided
> # by the '/usr/sbin/tcpd' server.
> #
>
> telnetd:LOCAL, smith486-25.pc.com
> fingerd, telnetd: pentium233.pc.com
> ypserv: 198.168.110.0
>
> The following is the hosts.deny file in /etc directory:
>
> #
> # hosts.deny This file describes the names of the hosts which are
> # *not* allowed to use the local INET services, as decided
> # by the '/usr/sbin/tcpd' server.
> #
> # The portmap line is redundant, but it is left to remind you that
> # the new secure portmap uses hosts.deny and hosts.allow. In particular
> # you should know that NFS uses portmap!
>
> portmap: ALL
> ypserv: ALL
>
> However, the "network" file normally located in the /etc directory is
> missing and I can't find information on how to create it.
>
> The following is the nsswitch.conf file in /etc directory:
>
> #
> # /etc/nsswitch.conf
> #
> # An example Name Service Switch config file. This file should be
> # sorted with the most-used services at the beginning.
> #
> # The entry '[NOTFOUND=return]' means that the search for an
> # entry should stop if the search in the previous entry turned
> # up nothing. Note that if the search failed due to some other reason
> # (like no NIS server responding) then the search continues with the
> # next entry.
> #
> # Legal entries are:
> #
> # nisplus Use NIS+ (NIS version 3)
> # nis Use NIS (NIS version 2), also called YP
> # dns Use DNS (Domain Name Service)
> # files Use the local files
> # db Use the /var/db databases
> # [NOTFOUND=return] Stop searching if not found so far
> #
>
> passwd: compat
> group: compat
>
> hosts: nis files dns
>
> services: nis [NOTFOUND=return] files
> networks: nis [NOTFOUND=return] files
> protocols: nis [NOTFOUND=return] files
> rpc: nis [NOTFOUND=return] files
> ethers: nis [NOTFOUND=return] files
> netmasks: nis [NOTFOUND=return] files
> netgroup: nis
> bootparams: nis [NOTFOUND=return] files
> publickey: nis [NOTFOUND=return] files
> automount: files
> aliases: nis [NOTFOUND=return] files
>
> The following is the resolv.conf file in /etc directory:
>
> search pentium233.pc.com
> nameserver 198.168.110.1
> nameserver 198.168.110.2
> nameserver 149.174.211.5
>
> The following is the yp.conf file in /etc directory:
>
> # /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 NISDOMAIN server smith486-25.pc.com
> domain NISDOMAIN broadcast
> ypserver smith486-25.pc.com
>
> The following is the ypserv.conf file in /etc directory:
>
> #
> # 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.
>
> sunos_kludge: no
> dns: no
>
> # 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 : Map : Security : Passwd_mangle
> #
> # * : passwd.byname : port : yes
> # * : passwd.byuid : port : yes
>
> # Not everybody should see the shadow passwords, not secure, since
> # under MSDOG everbody is root and can access ports < 1024 !!!
> * : shadow.byname : port : yes
>
> # 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
>
> I have tried to cd /var/yp and run make to generate the maps. However,
> this process gets half way done and gives an error message that it can't
> find the /etc/network file and stops. So if someone could please tell me
> what the /etc/network file should contain, I think it would solved my
> network problem on my 486-25 MHz computer.
>
> Thank you for helping me.
>
> Sincerely,
>
> David Smith
>
> Net-Tamer V 1.09.2 - Registered
>
>
>
>
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com http://archive.redhat.com
> To unsubscribe: mail redhat-list-request@redhat.com with
> "unsubscribe" as the Subject.
>
----------------------------------
Chris Manders
UNIX Systems Administration Group
CJManders@lbl.gov
----------------------------------
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
