Mailinglist Archive: opensuse-amd64 (470 mails)

< Previous Next >
Re: [suse-amd64] NIS Client OK?
  • From: Bjorn Tore Sund <bjornts@xxxxxxxxx>
  • Date: Wed, 3 Nov 2004 11:17:16 +0000 (UTC)
  • Message-id: <Pine.LNX.4.58.0411031145470.16329@xxxxxxxxxxxxxx>

Lennart,

If you'd quoted properly (http://www.netmeister.org/news/learn2quote.html)
someone else might have answered while I was away travelling. Or I might
have answered sooner as doing so would have required much less editing.

Top-quoting is evil, it may save you a little time but will deter a lot
of people from responding.


On Thu, 28 Oct 2004, Lennart Börjeson wrote:

> > I've got AMD64 NIS clients, have used SLES 8 in the past but have
> > migrated all of them to SuSE 9.1 over the last couple of months.
> > I never ran into problems of any sort.
> >
> > 1. Are you using broadcast or specific IP addresses to identify NIS
> > servers?
> > 2. What's the firewall setup on the clients?
> > 3. As you restart the ypbind daemon, does 'netstat -ut' on the server
> > show anything useful?
> >
> > Bjørn
>
> 1) Specific IP addresses or rather the names of the servers. I've tried
> broadcasting too. BTW, the configuration module in yast does not find any
> servers either if asked to scan for them.

Use IP addresses, not names. You don't want to be dependent on DNS
for NIS. Trust me on this.

Should be fine. You did set this up using yast2, I presume? Is the
client and server on the same subnet?

> 2) Default firewall, i.e. I've not configured anything explicitly. Basically a
> fresh install out-of-the-box of SuSE Pro 9.1. I believe this should equate no
> "no firewall"?

No, all the recent SuSE-versions have come with a firewall running.
Since it kills nfs I always disable it immediately and run my own
scripts. The firewall is fairly tight, and the default config seems
designed for the single machine home user. Whether it prevents NIS
I don't know - but your log snippet indicates that there's no stopped
traffic.

> 3) netstat on the server shows no incoming connections.

Anything in /var/log/messages?

> On the client, /var/log/messages says:
>
> Oct 28 07:29:07 sirius ypbind[23718]: broadcast: RPC: Timed out.
> Oct 28 07:29:12 sirius ypbind[23718]: broadcast: RPC: Can't encode arguments.
> Oct 28 07:29:52 sirius last message repeated 4 times
> Oct 28 07:30:52 sirius last message repeated 6 times
> Oct 28 07:31:52 sirius last message repeated 6 times
> Oct 28 07:32:52 sirius last message repeated 6 times
> Oct 28 07:33:52 sirius last message repeated 6 times
> Oct 28 07:34:52 sirius last message repeated 6 times
> Oct 28 07:35:52 sirius last message repeated 6 times
> Oct 28 07:36:52 sirius last message repeated 6 times
> Oct 28 07:37:02 sirius ypbind[23718]: broadcast: RPC: Can't encode arguments.
> Oct 28 07:38:06 sirius ypbind[23718]: broadcast: RPC: Timed out.
> Oct 28 07:38:25 sirius ypbind[23718]: broadcast: RPC: Can't encode arguments.

Is the portmapper running? 'ps aux | grep portmap' should get you the
answer to that. And you _are_ running ypbind in broadcast.

Bjørn
--
Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a
System administrator Fax: (+47) 555-89672 fractal; universal and
Math. Department Mobile: (+47) 918 68075 infinitely repetitive.
University of Bergen VIP: 81724
Support: system@xxxxxxxxx Contact: teknisk@xxxxxxxxx Direct: bjornts@xxxxxxxxx

< Previous Next >
This Thread
  • No further messages