Have you tried adding this line to your /etc/hosts.allow:
ALL : 192.168.0.
I had to do this to get nfs working on our Linux network. The local IP
addresses of our Linux machines are all 192.168.0.x. Good luck,
Hidong
[EMAIL PROTECTED] wrote:
>
> Hi,
>
> Pardon if these questions are contained in a FAQ somewhere; however, I'm
> confused about some issues.
>
> I installed Redhat 6.2 on one of our PCs here at work for the primary
> purpose of serving out some directories to NT PCs via NFS (since most of
> them have Hummingbird's NFS Maestro Solo installed). I also needed to serve
> those same directories out for NFS access from some target hardware running
> VxWorks. Here's what actions that I took:
>
> 1. From the GUI install, selected support for NFS.
>
> 2. After firing up Linux on the PC, I was able to determine that I needed to
> at least activate the NFS daemons. So, I fired up nfsd from
> /etc/rc.d/init.d/nfs and made appropriate links to that script in the
> runlevel subdirectories.
>
> 3. I then exported out a directory from the PC by placing an entry in
> /etc/exports and activating it by issuing an "exportfs -a" command.
>
> 4. Determined that I could hook up to this exported directory from another
> inhouse Sun machine on which I have an account.
>
> 5. After further research, determined that I probably needed to be running
> pcnfsd to allow the NFS clients on the PCs to hook up to this export.
>
> 6. Found pcnfsd on the redhat contrib site. Downloaded, installed via rpm,
> and activated it from the startup scripts.
>
> 7. Tried to hookup from an NT workstation running the Maestro client.
> Maestro can see the exported share from the Linux box. Unfortunately, I am
> getting an authorization error even though I am supplying a valid account
> for the Linux box.
>
> 8. Notes: Connectivity is not an issue since I can ping the Linux box from
> my PC.
>
> Questions:
>
> 1. Running "cat /proc/filesystems" does not list NFS as one of the
> filesystems. It only lists the following:
>
> ----------------------------------------------------------------------------
> ------
> ext2
> nodev proc
> iso9660
> nodev devpts
> msdos
>
> ----------------------------------------------------------------------------
> ------
>
> Would this imply that I need to recompile the kernel from sources to ensure
> support for NFS?? And that the check box in the install was only for
> inclusion of the nfs-related tools?? Btw, if this is true, why was I able to
> hook up from another Unix box?? I am probably going to try recompiling the
> kernel from sources next.
>
> 2. I got the binary rpm for pcnfsd from the redhat contrib ftp site with
> support for shadow passwords which I have enabled. Should I just recompile
> this daemon from sources instead of using that binary rpm?? If so, where can
> I get the shadow password library stuff, because as near as I can tell it is
> not included in the install and compiling pcnfsd from source seems to
> require this library.
>
> 3. I have not tried Samba yet for sharing out this resource; however, that
> may be a possibility soon as well. Is it going to be much of problem with
> that and that this PC is not a part of the NT domain the other workstations
> requesting that shared resource would be??
>
> 4. Are there any good resources (especially relating to pcnfsd) on the Web
> anywhere?? I have a number of NFS-related stuff @linuxdoc.org and done
> searches at www.google.com/linux. I was just wondering if there was anything
> more concise (or related). Maybe someone else has gone through these types
> of travail.
>
> Any information, hints, clues, solutions, etc. would be greatly appreciated.
>
> thanks,
> mark
> --------------------------------------------------------------
> email(work) => [EMAIL PROTECTED]
> email(home) => [EMAIL PROTECTED]
>
> ... Unix IS a user friendly O/S ...
> (It's just picky about its friends)
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
