MS Services for Unix permission problems

[Ric Werme]

> For various reasons I'm trying to get Microsoft Services For Unix's (SFU) NFS Server setup so a unix system can mount files on the PC.  I have Linux and Solaris NFS clients to play with.
> 
> On Solaris I get this error: 
> NFS access failed for server blahblah: error 7 (RPC: Authentication error)

This generally indicates that the MOUNT protocol server (part of the NFS
server) doesn't like the client for some reason.  These are typically
things like IP address doesn't match node name or that the requested object
(file system, directory, file) isn't exported to the client.  They can be
a tad annoying to resolve.

> /net/blahblah/NFS: I/O error
> total 1
> 
> Linux gives this:
> ls: /net/blahblah/nfs: Permission denied

Ought to be about the same.

> I'm using IP addresses here.
> SFU is set to allow anonymous and root access

Are there options (on SFU) for about IP addresses, names, permitted clients,
etc?


> Permissions on visible from the unix side are 777

Shouldn't matter, you aren't getting past MOUNT, so the kernel is never
given the data needed to create the mountpoint.


> I've run wireshark on the Linux side and see the ACCESS reply is 0x00 (deny all)

What's wireshark?  What's ACCESS?  There's a NFS V3 protocol command named
ACCESS, but I don't think you're getting that far.

You're best off looking at ethereal/tcpdump traces between the two.

> Any one else have to work with SFU? 

In my case, only from the context of making sure it worked with Tru64 Unix's
NFS client.

    -Ric Werme