bdf shows RPC: Authentication error

[ClaudiaAmado]

We're mounting a file system in a Windows 2000 server.
When running bdf in the HP-UX, the system shows the messages:
NFS access failed for server 10.142.176.51: RPC: Authentication error
10.142.176.51:/PDSCBA_DATA

Any idea about how can I check what's going on?
Thank you

[Denver Osborn]

How was it exported from the w2k server? Are you running bdf as root? Have you tried to run bdf as a non-root user?

-denver

[ClaudiaAmado]

Thank you for you reply!

I executed bdf as root and also as a non-user. Both show me the same message.

Here are the line from /etc/fstab:

10.142.176.51:/PDSCBA_DATA /opt/avaya/pds/imon/data nfs rw,suid 0 0

[Dave Olker]

Hi Claudia,

There are very few true RPC-related reasons why an NFS mount would generate an authentication error. The most common reason is if the user issuing the RPC request belongs to more than 16 groups. That would indicate the problem is on the client - where the only fix would be to remove the user from some of the groups they belong to.

However, when you add Windows to the mix, there are probabaly a dozen reasons why a Windows server would reject a request for authentication reasons.

My first step would be to determine if the problem is on the client side or the server side. Probably the easiest way to do this would be to try mounting an NFS filesystem from a different (preferably non-Windows) server and see if you get RPC authentication errors with every NFS filesystem or only with NFS filesystems exported by Windows systems. If the client works correctly with other servers then most likely you're going to be investigating the Windows server.

Regards,

Dave

[ClaudiaAmado]

Hi Dave!

I can do this test.

By your knowledge, what should be the right sequence/command to mount the filesystem?

[Dave Olker]

Hi Claudia,

If you have another HP-UX system you can test with, simply export one of the filesystems like /tmp - either manually via the exportfs -i command or by adding an entry to the /etc/exports file and using the exportfs -a command, then create an empty directory on the HP-UX client like /test and try mounting the filesystem with a command like:

# mount :/tmp /test

Then do a bdf and see what happens.

Regards,

Dave

[Eric Raeburn]

Claudia,

Have you mounted the Windows system with NFS or CIFS? If CIFS, whoever issues the bdf command must first be authenticated by the server in order to access the mountpont, even to simply get info on the mount. This is usually accomplished with the "cifslogin" command.

-Eric

[Eric Raeburn]

Oops, just noticed the "nfs" option in your /etc/fstab file; please ignore my comments about CIFS.

[ClaudiaAmado]

Eric

Thank you for your answer.
I shared another directory in another Windows server. I set full permissions.
I can perfect access the directory in both servers.
The message that appears in df command looks like a warning ... but it bothers me ... I'd like to take if off ...

All the information is on the /etc/fstab
I have no idea about what else I can change in the Windowns server to avoid this message.

Is there any other file that need to be configured in the HP-UX side?