Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NFS mount permission denied - Solaris 10 servers (newbie question)

2,149 views
Skip to first unread message

underh20

unread,
Nov 24, 2010, 7:56:10 PM11/24/10
to

We are trying to NFS mount a file system securely from serverA to
serverB and to serverC. There is a valid entry in /etc/dfs/dfstab
file at serverA and the command "shareall" is issued. For some
reason, we are getting "permission denied" when trying to mount the
serverA's NFS file system "/data" at serverB or serverC. The local
directory "/serverA-DATA" has been created at serverB and serverC
beforehand.

Can anyone shed some light on how to resolve the problem ? Below are
the commands output. Thanks, Bill


<At serverA>

# cat /etc/dfs/dfstab

share -F nfs -o rw=serverB /data
share -F nfs -o rw=serverC /data

# shareall

<At serverB>

# mount -F nfs -o rw serverA:/data /serverA-DATA
nfs mount: mount: /serverA-DATA : Permission denied


<At serverC>

# mount -F nfs -o rw serverA:/data /serverA-DATA
nfs mount: mount: /serverA-DATA : Permission denied

chuckers

unread,
Nov 25, 2010, 1:02:42 AM11/25/10
to

Name resolution failure for serverB and serverC on serverA perhaps?

If you use IP addresses, does it work?

Mike Marshall

unread,
Nov 25, 2010, 7:32:58 AM11/25/10
to
chuckers <chuck...@gmail.com> writes:
>Name resolution failure for serverB and serverC on serverA perhaps?

I usually use snoop to watch the failure, and it usually turns out
to be name resolution...

-Mike

Oscar del Rio

unread,
Nov 25, 2010, 9:43:15 AM11/25/10
to

I usually ssh from the client to the server and check "who am i" for
hostname. That's usually the hostname that has to go in dfstab. Often
it is the full domain name "hostname.domain.name"

Rick Smith

unread,
Nov 26, 2010, 5:49:14 PM11/26/10
to
On Nov 25, 8:43 am, Oscar del Rio <del...@mie.utoronto.ca> wrote:
> On 11/25/10 07:32 AM, Mike Marshall wrote:
>
> > chuckers<chucker...@gmail.com> writes:
> >> Name resolution failure for serverB and serverC on serverA perhaps?
>
> > I usually use snoop to watch the failure, and it usually turns out
> > to be name resolution...
>
> I usually ssh from the client to the server and check "who am i" for
> hostname. That's usually the hostname that has to go in dfstab. Often
> it is the full domain name "hostname.domain.name"

telnet or ssh to server A from servers B and C, on server A do last -a
this will show you how you appear to server A and you might see the
FQDN of server B and C or you might just see an IP addess, in either
case, Use what you see in the share options, so if you see in last -a
XXX XXX XXXX B.mydomain.com
XXX XXX XXXX C.mydomain.com

do
share -F nfs -o rw=B.mydomain.com /data
share -F nfs -o rw=C.mydomain.com /data

and just to be safe try doing share /data

0 new messages