HP-NAS share authentication error

[Mike Linger_2]

In summary, I have an isolated LAN.

1 HP-UX 11.23 Itanium server with an NIS master.

1 hub.

1 Proliant DL100 disk array running Windows 2003 Server.

I have one NFS2 share on the Windows box. HPUX users can't gain access to a file until root has accessed the file first. If I unmount the share and remount it, then root will have to access each file again before any users can gain access.

How do I fix this?

Explicit details below:
Configuration:
HP-UX 11.23 rx5670 server with two Ethernet ports. One port is on the building network (129.4.204.XXX subnet). The building network does not seem relevant to our NFS shares problem. I tried the following without the building network and obtained the same results. The other port is on a 200.0.0.XXX subnet. This is the segment of interest.
The 200.0.0.XXX subnet consists of the HP-UX box above, one hub, and a Proliant DL100 disk array running Microsoft 2003 Server.
I’ve enabled NIS on the HP-UX box. NIS+ is not enabled.
The Windows box is able to query my NIS domain. I’ve explicitly mapped:
User: Administrator to root
Group: Administrators to root
Group: Users to users

The Windows NFS server has NFS3 disabled. I get worse results with NFS3 enabled.
I have one NFS share on the Windows box. “F:\test” has an NFS share name “test” . This is only shared with an NFS protocol. “F:\test” has RW access, root access, and the Users group has full-control.
“F:\test” contains one textfile: “New Text Document.txt”. “New Text Document.txt” contains the following text:
This
is
a
test.

The following sequence is deterministic.
‘# ‘ denotes my root login
‘bash-2.04$’ denotes my user login.
// denotes my comments

# mount 200.0.0.1:/test /mnt/test // no errors
bash-2.04$ ls /mnt/test // empty directory
# ls /mnt/test // root sees a non-empty directory
New Text Document.txt
bash-2.04$ ls /mnt/test // user sees a non-empty directory
New Text Document.txt
bash-2.04$ cat /mnt/test/* // user fails file read permissions
NFS lookup failed for server 200.0.0.1: RPC: Authentication error
cat: Cannot open /mnt/test/New Text Document.txt: I/O error

# cat /mnt/test/* // root can read the files
This
is
a
test.

bash-2.04$ cat /mnt/test/* // from now on, users can read files
This
is
a
test.

As long as root touches the files first, subsequent users can perform the corresponding IO operation on the same files.
Every time I mount the share, I

[Steven E. Protter]

Perhaps build a "auto" mount by root of the NAS server into /etc/fstab

Here is an example:

//192.168.0.20/web /webtemp smbfs credentials=/etc/.smbpasswd 0 0


This is a samba example but if you change the smbfs to nfs it might help.

.smbpasswd has two lines user and password and permissions are VERY tight.

SEP

[Mike Linger_2]

I'm trying to avoid a manual configuration of system files.

It doesn't look like I'm having a mount problem. I had the automount configured through sam at first, but I disabled it when I started to troubleshoot. My manual mount command never returns an error message:

mount IP:/sharename /mountpath
bdf claims that the share is mounted.

As long as root accesses every file first, then subsequent users don't have any problem.

If a user tries to access the file first, I get this message:

NFS lookup failed for server 200.0.0.1: RPC: Authentication error

Does this mean that I've been denied access, or does it mean that the authentication experienced a breach in protocol (bug)?