Shawn wrote: > > On Mon, 2003-04-21 at 16:27, Antoine Martin wrote: > > Sorry, but I meant on the server. > > The client can use portmap to find out the port numbers and portmap can > > be allowed through the firewall as it uses a specific port (111) > > But the ports for the various nfs daemons are dynamically allocated by > > portmap. > > You should be able to set port=0 then, and that will cause it to query > the remote host's portmapper for the port number to use. If the remote > host's NFS deamon is not registered with its portmapper, the standard > port number of 2049 will be used instead. > > > > > > > > * Where is the tool for configuring NIS? > > > > > > System Settings->Authentication or: > > > > > > authconfig-gtk > > > > Sorry, I meant on the server side again... > > Client-side is there, which is why I am wondering why the server side > > isn't. > > I'm not sure what you're after here. Why would there be a tool on your > local box to configure NIS? If you're talking about hosting NIS with > RedHat 9, well then you're looking at the wrong product, I believe the > Enterprise Server edition has NIS services, someone correct me if wrong. Shrike: ypserv-2.6-2.i386.rpm docs: http://www.tldp.org/HOWTO/NIS-HOWTO/index.html -- toby
