Very Computer

by **Jean-Michel FRENO** » Thu, 31 May 2001 23:16:19

Bonjour,

I got the same mess than ossama_sultan. (with RedHat 7.1)

Trying further I run ypbind in debug mode and got this :
ping host `my.server.ip.address` , domain 'MyDomainName'
host `my.server.ip.adresse` doesn't answer
The network is runing and I can ping all the machines.
`my.server.ip.address` do the job for all the other clients.

I thought ypserv on `my.server.ip.address` was too old and I run ypserv
on the machine with the new system. ypbind can't bind my domainname no
more.

I am very sad :-(

--

: .... Jean-Michel Frnod
: : Laboratoire d'Informatique de Paris 6
...:. . . :.. C471 8 rue du capitaine Scott Paris XV
: : : : : : : : (boite 169) 75252 PARIS cedex 05
.. : : :: 33 (0)1 44 27 70 06

by **Dean Thompso** » Fri, 01 Jun 2001 00:18:45

Hi!,

Quote:> I got the same mess than ossama_sultan. (with RedHat 7.1)

> Trying further I run ypbind in debug mode and got this :
> ping host `my.server.ip.address` , domain 'MyDomainName'
> host `my.server.ip.adresse` doesn't answer
> The network is runing and I can ping all the machines.
> `my.server.ip.address` do the job for all the other clients.

> I thought ypserv on `my.server.ip.address` was too old and I run ypserv
> on the machine with the new system. ypbind can't bind my domainname no
> more.

Check to make sure that it isn't a firewall which is stopping you from
connecting to your NIS master server or that the server doesn't have any
hidden firewall rules either. You might like to flush your input chain and
make sure that there are no entries in there and see whether a ypbind can be
successful. Additionally, make sure that the ypserver hostname is specified
in the appropriate /etc/yp.conf file and that the IP address of this server
can be found in the /etc/hosts file.

If possible, try putting your ypbind into debug mode and see whether or not
you can identify the problem.

See ya

Dean Thompson

Very Computer

NIS problem

NIS problem

NIS problem