Re: Solaris NIS server and Linux NIS client : problems
From: Srihari Raghavan (srihari.raghavan_at_gmail.com)
Date: 09/02/04
- Next message: Dragan Cvetkovic: "Re: Solaris NIS server and Linux NIS client : problems"
- Previous message: Dennis Grevenstein: "Re: Linux, *BSD, etc. OS which uses UltraSPARC's LSB mode ?"
- In reply to: Juhan Leemet: "Re: Solaris NIS server and Linux NIS client : problems"
- Next in thread: Dragan Cvetkovic: "Re: Solaris NIS server and Linux NIS client : problems"
- Reply: Dragan Cvetkovic: "Re: Solaris NIS server and Linux NIS client : problems"
- Reply: Juhan Leemet: "Re: Solaris NIS server and Linux NIS client : problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 2 Sep 2004 08:01:14 -0700
Hi Juhan
Thank you very much for your reply. I have tried out all the
changes and commands and still, there seems to be some issue. I am
suspecting the server side settings. If you have any other comments,
pl. let me know.
a. Changed nsswitch.conf to only compat..values
b. Changed nsswitch.conf for hosts values.
=====
passwd: compat
shadow: compat
group: compat
#hosts: db files nisplus nis dns
hosts: nis dns files
=====
Here are the outputs:
/var/log/messages output
Sep 2 09:59:56 spock ypbind: Setting NIS domain name <domain>:
succeeded
Sep 2 09:59:56 spock ypbind: ypbind startup succeeded
Sep 2 09:59:57 spock ypbind: bound to NIS server odin.<domain>
Sep 2 09:59:57 spock autofs: automount startup succeeded
Sep 2 09:59:57 spock automount[798]: starting automounter version
3.1.7, path = /fs, maptype = file, mapname = /etc/auto.nfs
Sep 2 10:00:02 spock yppasswdd: rpc.yppasswdd startup succeeded
Sep 2 10:02:46 spock login(pam_unix)[1115]: check pass; user unknown
Sep 2 10:02:46 spock login(pam_unix)[1115]: authentication failure;
logname= uid=0 euid=0 tty=pts/0 ruser= rhost=cherry.<domain>
Sep 2 10:02:49 spock login[1115]: FAILED LOGIN 1 FROM cherry.<domain>
FOR <login>, Authentication failure
Sep 2 10:02:52 spock login(pam_unix)[1115]: session opened for user
<another_login> by (uid=0)
Sep 2 10:02:52 spock -- [1115]: LOGIN ON pts/0 BY <another_login>
FROM cherry.<domain>
[]$ ypwhich
<server>.<domain>
[]$ ypwhich -m
Can't get map list for domain <domain>. Reason: Can't bind to server
which serves this domain
[]$ ypcat -h <ipaddr> passwd
No such map passwd.byname. Reason: Can't bind to server which serves
this domain
Thanks in advance
Sri
Juhan Leemet <juhan@logicognosis.com> wrote in message news:<pan.2004.09.02.03.06.31.197302@logicognosis.com>...
> On Wed, 01 Sep 2004 10:07:29 -0700, Srihari Raghavan wrote:
> > b. Changed nsswitch.conf
> > passwd: compat files nis
> > shadow: compat files nis
> > group: compat files nis
>
> Who told you to do that? All of the examples I've ever seen say to use
> just compat, and that's what I use with SuSE Linux (currently 9.1), i.e.:
>
> passwd: compat
> shadow: compat
> group: compat
>
> > hosts: nis files dns
>
> That seems to be the way to set it up on Linux, or you might want to put
> dns after nis and before files (for consistency with Solaris?). On Solaris
> I don't have dns in the hosts list, but I can resolve internet host names.
> I think there is a subtle difference in the lookup of host names between
> Linux and Solaris? I believe Solaris automagically "falls back" to using
> DNS if the nis lookup does not work? Linux does not seem to do so? In any
> case, I've found that I need to have dns in hosts list on the Linux side.
>
> Also, I have found (but not tracked down) that if one of my Solaris
> machines refers to ypserv from a Linux machine (i.e. ypwhich gives a
> Linux machine name), then it cannot resolve DNS names. I have not tracked
> that problem down. Instead, I have made sure to refer to Solaris ypserv.
>
> BTW, have a look at the /etc/nsswitch.* files on a Solaris system. There
> are several templates there, for: files, nis, dns, ldap, nisplus.
>
> > 1. ypwhich shows the NIS server's DNS name (fully-qualified)
> > 2. ypcat passwd shows error
> > No such map passwd.byname. Reason: Can't bind to server which
> > serves this domain
>
> This looks strange. The ypwhich should show the server, and then ypcat
> should get the map from that server. Did the other person rebuild the
> updated maps on the master server? Did he push them out to all server(s)?
> Have a look at:
>
> ypwhich -m
>
> Which will list all the maps and their master server(s).
> Is passwd.byname in there? If not, why not? Fix it.
>
> BTW, does your hosts map give both FQDN and hostname for each machine?
> Try doing a:
>
> ypcat -h <hostname> <map>
>
> Try different values in <hostname> (FQDN, hostname, IP address). All of
> those variants should work. If not, fix it/them.
- Next message: Dragan Cvetkovic: "Re: Solaris NIS server and Linux NIS client : problems"
- Previous message: Dennis Grevenstein: "Re: Linux, *BSD, etc. OS which uses UltraSPARC's LSB mode ?"
- In reply to: Juhan Leemet: "Re: Solaris NIS server and Linux NIS client : problems"
- Next in thread: Dragan Cvetkovic: "Re: Solaris NIS server and Linux NIS client : problems"
- Reply: Dragan Cvetkovic: "Re: Solaris NIS server and Linux NIS client : problems"
- Reply: Juhan Leemet: "Re: Solaris NIS server and Linux NIS client : problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|