[TriLUG] NFS,Autofs,NIS and FC2

[Kevin Flanagan]

First, thanks to Jon and Matthew, so far I did get some info out of
systems.


The user is not a local user, and the mount point exists, and I can
mount things after login just fine, but my issue seems to be YP.  Here's
the last couple of entries in the /var/log/messages

Jun  9 06:34:55 www ypserv[1607]: refused connect from 192.168.0.105:975
to procedure ypproc_all (flanagannc,auto.master;-4)
Jun  9 06:36:16 www ypserv[1607]: refused connect from 192.168.0.105:955
to procedure ypproc_all (flanagannc,x;-4)


This has at least gotten me to the point where I believe the "problem"
to be NIS security.  I don't know why it would be an issue with the new
systems, and not the old ones but...


Thanks for the help so far!



Kevin


On Wed, 2004-06-09 at 00:18, Jon Carnes wrote:
> Is "kevin" also a local user on the FC2 system? 
> 
> Do the mount points exist? 
> 
> Can you manually mount the drive after you login?  If not then it's
> probably a overly paranoid security issue where the user is not allowed
> to force an NFS mount.
> 
> I assume that you've tested the NIS data using ypcat and letting it list
> our the passwd and group files.
> 
> Hope that is somewhat helpful - Jon
> 
> On Tue, 2004-06-08 at 19:09, Kevin Flanagan wrote:
> > Hey all,
> > 	I currently have the following issue that may be related to changes
> > with FC2.  The config outlined below works just fine with FC1, but
> > doesn't completely work with FC2, I can't figure it out.
> > 
> > 
> > A Clarkconnect system as my master NFS and NIS server
> > uname -a yields "2.4.20-28.9 #1 Thu Dec 18 13:45:22 EST 2003 i686 i686
> > i386 GNU/Linux" - This is 192.168.0.206
> > 
> > I have an exports as such,
> > 
> > /kits           192.168.0.0/255.255.255.0(rw,sync,no_root_squash)
> > /home           192.168.0.0/255.255.255.0(rw,sync,no_root_squash)
> > 
> > 
> > /kits is mounted as /kits on all systems
> > /home is mounted as /homes/users
> > 
> > auto.misc is as follows
> > kits            -rw,soft,intr 192.168.0.206:/kits
> > stuff           -rw,soft,intr 192.168.0.108:/stuff
> > 
> > 
> > auto.homes is as follows
> > users   -rw,soft,intr,no_root_squash  192.168.0.206:/home
> > 
> > 
> > auto.master is as follows
> > /misc   /etc/auto.misc  --timeout=60
> > /homes  /etc/auto.homes --timeout=60
> > 
> > 
> > 
> > My NIS map has my home directory as /homes/users/kevin
> > 
> > 
> > 
> > I can log into the FC2 system as root just fine, when I try to log on as
> > myself I get told that my homedir isn't available.  When I log on as
> > root I have the stuff under /misc available just fine, kits under it
> > etc.
> > 
> > Did something change with FC2 that would make this break?
> > 
> > 
> > TIA!!!
> > 
> > 
> > 
> > Kevin
> > 
> > 
> > 
> > 
-- 

+--------------------------------------------------------------+
If you never see anything that offends you, you aren't living in a free
society

Kim Campbell - Former Canadian Prime Minister
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://www.trilug.org/pipermail/trilug/attachments/20040609/ebfcdddc/attachment.pgp>