On 4/13/07, David <rivera01 at sbcglobal.net> wrote: > Our company due to the extremely locked down networks is limited to using > public NFS when crossing over from one DMZ to another. > > > The problem I am seeing is on the client that I use public NFS on to mount a > share, it hangs the logins of any user who attempts to login, this is if I > put an entry in the /etc/vfstab for the public NFS share. If I use the mount > command that excludes writing to the /etc/mnttab, then everything works just > fine. The problem is the users of the server do not want it that way because > they are not able to see the filesystems mounted when they do a df -h.
It could be that it is trying to check quotas. Create an empty .hushlogin file in a user's home directory and log in as that user. If this works then you may want to add the noquota mount option or comment the calls to quota from /etc/profile et. al. If that doesn't work, run "snoop -d <interface> host <nfsserver>" on the DMZ machine to see what kind of traffic is being sent to the NFS server when logging in. You can figure out which interface is being used (in most cases... this is not 100% accurate) with "route get <nfsserver>". Mike -- Mike Gerdts http://mgerdts.blogspot.com/
