I have made sure all files and mount locations have open access (chmod
777). The userid on the Solaris box that I am doing the mount through
is a member of the system group, and that userid is the same on both
server and client boxes. I am unable to find any reason why I would
get permission denied errors. If anyone has insights, please let me
know.
Thanks,
Mike Cooper
"Mike Cooper" <bid...@concentric.net> wrote in message
news:c0bba8a2.02072...@posting.google.com...
I've hit a similar problem with linux, and the howto told me to set
the following option on AIX:
nfso -o use_reserved_ports=1
This makes AIX use lower then 1024 portnumbers for the NFS client.
Which means you are positively identified as root on the system.
good luck,
Maarten Kreuger
This refers to using a Linux server with an AIX client. Mike is using an
AIX server and a Solaris client. And in any case, I do not think that
the high source port problem applies to Solaris (but will test the point
tomorrow).
The Solaris man page states that only "a super-user" can mount
filesystems but doesn't define what a super-user is. There is no group
"system" on my Solaris box which is a fairly default Solaris 9. Mike,
what happens if you try it as root? I'll test this tomorrow too.
Regards, Ian
I have both Solaris 7 and 8 machines mounting from AIX 4.3.3 with
less problems than from a NetApp.
1) Please be more carefull in quoting the error message. We can't tell
if the mount is trying to happen and the server is denying it, or if
you are being denied mount rights because you are not root. Being in
the system group isn't going to do if for you because /usr/sbin/mount
is not suid and is root.bin anyway. As someone else has pointed out,
you need to do this as root.
2) If you really are trying the mount properly, and still getting
an error, it could be a DNS issue - as someone else implied by
suggesting to hack the /etc/hosts files - better to fix DNS, but at least
that would isolate the problem.
3) there is also a lower probablilty possibility that you need to run
the following cleaning procedure on the AIX box:
stopsrc -g nfs
rm -r /etc/sm /etc/sm.bak /etc/state
startsrc -g nfs
The older AIX used to need this in dynamic environments, but I haven't
run into that issue lately.....
Cheers.
--
"I'm a big fan of ignorance based techniques, because humans
have a lot of ignorance, and we want to play our strong suit."
Eric Lander New Scientist
I have the same Problems on a SuSE SLES7 Linux box (client) and AIX
4.3.3 (server).
On AIX 4.3.2 it works fine.
You get the same error message if the NFS Server can´t resolv the client
Hostname. But this is not the Problem.
Thanks Jörg
I tested this, and can confirm that Solaris is not fussy about an AIX
client's high source port numbers.
> The Solaris man page states that only "a super-user" can mount
> filesystems but doesn't define what a super-user is. There is no group
> "system" on my Solaris box which is a fairly default Solaris 9. Mike,
> what happens if you try it as root? I'll test this tomorrow too.
Again, it worked fine for me with an AIX server and Solaris client,
issuing the mount as root.
AIX 4.3.3ML09 and Solaris 8 Intel Edition.
Regards, Ian
Ah yes, my mistake. Mixed up the client and the server. And speaking
of servers.... Mike, you DID start the nfs servers on your AIX box,
did you?
start the daemon with: startsrc -g nfs
and check the status with: lssrc -g nfs
and check your exports with: exportfs
Portmapper is running? test with: lssrc -s portmap
If all else fails, see what you can make of: rpcinfo -p
Oh, and one especially tricky one: If you are exporting the root of a
filesystem, have a peek at the mountpoint underneath it. The
permissions of the mountpoint influence searches in the root of the
filesystem. The permission of the root of the filesystem may be set to
777, but that does not change anything when you access it from a lower
directory... You have to unmount it and check.
If this doesn't help, call IBM support will you?
Good luck,
Maarten