An interesting sidenote -
Things do work fine on another test setup consisting of C5 64-bit and an
Intel NIC. The problem C5 64-bit system has a Broadcom 57xx NIC.
I may opt to change NICs and see if that makes any difference...
Scott
On Thu, 18 Oct 2007, John Allen wrote:
When you do the ypinit -s, what name do you provide for the server?
It must match the name the server expects, so if the server host name is nis,
then you
do
ypinit -s nis.domainname
Scott Ehrlich wrote:
On Wed, 17 Oct 2007, sam wrote:
so...
if i'm understanding:
-you have a 32bit NIS server that you've
Correction here - server is 64-bit RHEL 5 Server. All machines are full,
out-of-box, unpatched systems, with no Internet connection.
Working clients are 32-bit. Problem machine is 64-bit CentOS 5 client.
configured for your network.
-you are not running dns, but are instead using /etc/hosts,
and /etc/resolv.conf on your boxes
-you have a couple of 32bit clients that can attach to the
NIS server, and that you can log against. you can run
'ypcat passwd' on these machines with no issues..
-attaching a 64bit machine as a NIS Client which you've
configured as best you can, is giving you errors...
I just had a conversation with a Sr. Redhat Tech support eng, where he was
telling me that there might be an issue with my situation that might be
related to the fact that the server is 64 bit, and the slave is 32bit...
might not be related.... but hmm...
can you post your ypserv.conf, as well as your yp.conf files
I'll have to check on my ypserv.comf file - I don't recall having edited
that.
yp.conf on the server is:
ypserver 127.0.0.1
yp.conf on the client is:
domain my-nis-domain server ip-of-server
Scott
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Scott Ehrlich
Sent: Wednesday, October 17, 2007 3:58 PM
To: CentOS mailing list
Subject: Re: [CentOS] NIS problems
On Thu, 18 Oct 2007, Clint Dilks wrote:
Scott Ehrlich wrote:
I've got a RHEL5 server acting as a NIS/NFS server, and connected one C5
machine just fine.
I'm trying to connect another, and for the life of me, cannot figure out
why NIS won't bind. NFS works fine. ypbind just hangs. I disabled
SELinux and the firewall. I just cannot get it to bind.
Ideas?
Hi do you have the appropriate entry in /etc/hosts for ypserv on NIS
Server ?
Yep. This is on a small lan - /etc/hosts acts as local dns.
The error is the one when ypinit -s server hasn't been run. I've had two
successful runs on 32-bit C5 adding said 32-bit hosts to the network, but
this one 64-bit C5 system is giving me the NIS problems. I can ssh, ping,
and doing anything else I want. Again, the 32-bit hosts work fine against
the server. This one 64-bit machine is simply giving me the NIS
headaches.
Thanks for any/all ideas.
Scott
Thanks.
Scott
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
--
John Allen mailto:[EMAIL PROTECTED]
CodeMountain http://www.codemountain.net
Ubuntu 7.04, kernel 2.6.20-16-generic
up 6 days, 23:51, 16 users, load average: 0.98, 0.88, 0.95
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos