GuardianOS NFS Issues

[tje]

Hi all (again)
Anyone using NFS with GuardianOS?
Having a weird issue whereby I create a share called Tom, path /tom, try and nfs mount it, and I get errors stating that I

refused mount request from 10.100.100.1 for /sharestom (/): no export entry rpc.mountd 08/06 20:17:22

whereas the path is actually /tom

I've tried this with a path of /sharestom, but when mounting the share, I get /sharessharestom - go figure. Looks like a typo somewhere inside GuardianOS to me - anyone else seen this?

[tje]

just to add that I use NFS on snapos with no problem

[blue68f100]

Are you using the latest OS version?

Adaptec has released a lot of updates.

Have not tried NFS so I can't help you there. Have you searched their knowledge base?

[tje]

Yes, using 4.4.045 - have searched their KB to no avail :/
Thanks for the quick reply.

[blue68f100]

Have you tried a reboot of the server since you added the user share. Sometimes things are not completly setup instantly, depending on usage. And reboots cleans everything up.

[tje]

Yeah - tried all that too. Have recreated the share, moved it, changed paths, names, you name it.
If I do this on a SnapOS unit it "just works". Its weird

[Phoenix32]

Out of this Hardware guys league... Sorry...

[blue68f100]

Are you using the guide to add a users/shares or manually?

[blue68f100]

Ok, Located a Knowledge base article by SnapAppliance on NFS on SnapOS. Maybe this will shine some light. You may see something that was missed during the setup. Remember this was for Snap OS, there may be one for Guardian OS.

NFS User Authentication

UNIX NFS users
NFS users from UNIX computers or multi-user systems must be associated with a local user. See NFS User Configuration below. UNIX users are authenticated on the UNIX system but have the same rights as their associated local user.

GUEST users
By default, users who you have not entered in the server's configuration can connect automatically with GUEST privileges.

NFS User Configuration
NFS users require some special configuration steps. The NFS protocol identifies its users by a combination of host IP address and user identification (UID) number.

The host IP address is the IP address of the system from which the user is connecting. The Snap Server allows grouping of multiple hosts together by means of the IP address mask.

All UNIX users are assigned a UID. After authenticating a user based on the user name and password, UNIX uses the UID to identify the user internally or when issuing requests to an NFS server.
When configuring a Snap server local user, the user may be associated with the identity of one or more NFS users. This allows the Snap Server to recognize an NFS user as a local user. By virtue of this recognition, the NFS user is granted the same privileges on the Snap Server as the corresponding local user.
For example, user Joe has user account JOEUSER on a UNIX system. To allow Joe to access files on your Snap server, first create a Snap server local user account named JOEUSER and assign it a password. The user name and password need not match those on the UNIX host. To make the Snap server local user account usable from NFS, create an NFS property for the account, using Joe's UID and the IP address from the UNIX system.

Each local user can have one or more NFS properties. For each of these properties, a UID, an IP address, and an IP mask must be specified.
The UID is assigned by a UNIX system to each of its user accounts. (The UID may be displayed by looking at the /etc/password file, in an NIS password map, or by logging into the user account and running the id utility.)

The IP address is the IP address of the host (or group of hosts) the user will connect from. The IP address mask is used to identify this as either a single address or a range of addresses (to include all systems in a given subnet).
The IP address mask ties a UID to a set of UNIX systems that share a common security database. It determines what portion of the IP address the Snap server will use to identify the NFS user.

For example, an NFS entry with IP 192.168.1.1 and address mask of 255.255.255.255 (default) associates the specified UID to one IP.
By changing the address mask to 255.255.255.0, the user with the specified UID from all clients in the 192.168.1.X subnet is recognized as the same Snap user.
Each NFS property must differ from the other NFS properties defined in your Snap server by at least one of the following:

A unique IP address (or range of IP addresses, as determined by combining the IP address and the IP address mask)
A unique UID

For example, multiple users from the same UNIX host may be added. All of these users share the, same IP address. However each user's UID must be different. Similarly, two separate users may have the same UID on their respective UNIX hosts. Their host's IP address, however, will be different. In either of these cases, the IP address and the UID may be combined to specify a unique NFS property for these users.


Setting Up NFS Properties for a User
To set up NFS Properties for a user:
1. On the Security menu, click Users to display the Users page.
2. Select the user name in the Users list.
3. Click NFS to display the NFS Properties page.
4. Add or delete the user's NFS entry, and then click OK.

[tje]

Heya
Thats looks helpeful thanks. Been busy here so not played any more - will try over the weekend.

Thanks again.