david@phys.anu.oz (10/24/90)
I am having problems NFS mounting Ultrix (3.0 and 4.0) file systems on AIX 3.1. The following message is produced even when the appropriate permissions are granted on exported directories. # mount rsphy1:/users /mnt mount: server rsphy1 not responding: RPC: Authentication error; why = Invalid client credential nfsmnthelp: rsphy1: The file access permissions do not allow the specified action. mount: giving up on: rsphy1:/users The file access permissions do not allow the specified action. I successfully mount between DECStations running Ultrix 3.0 and 4.0 and also between RS6000/320s including jfs and cd-rom file systems. I can also mount from AIX to Ultrix successfully, and both ways SUNOS-AIX and SUNOS-Ultrix. Also Ultrix-Connection 1.3 on VMS will mount on Ultrix and AIX. Has anyone out there successfully mounted Ultrix to AIX - are there any patches required/hacks to passwd & group files/whatever? Local reps from both IBM and DEC have been unable to help so far. Please post to "david@phys.anu.edu.au" if you can help. Thanks in advance, David Baldwin Head, School Computer Unit Research School of Physical Sciences Australian National University Canberra, Australia Phone: intl+61+6+2490104 or (06) 249 0104 Fax: intl+61+6+2491884 or (06) 249 1884 Internet: david@phys.anu.edu.au
jpe@egr.duke.edu (John P. Eisenmenger) (10/24/90)
From article <1990Oct23.175013.1@phys.anu.oz>, by david@phys.anu.oz: > I am having problems NFS mounting Ultrix (3.0 and 4.0) file systems on AIX > 3.1. The following message is produced even when the appropriate > permissions are granted on exported directories. > > # mount rsphy1:/users /mnt > mount: server rsphy1 not responding: RPC: Authentication error; why = > Invalid client credential > nfsmnthelp: rsphy1: The file access permissions do not allow the specified > action. > mount: giving up on: > rsphy1:/users > The file access permissions do not allow the specified action. > Has anyone out there successfully mounted Ultrix to AIX - are there any > patches required/hacks to passwd & group files/whatever? The problem is in the type of ethernet packet in use. Your RS6000 is using Xerox Ethernet, whereas you Ultrix station is using IEEE 802.3. If you change your RS6000 to use IEEE 802.3 things will work. For some reason this doesn't show up in other protocols, and most of the mounting process actually goes okay. It's when the actual ..MOUNT.. request gets sent that the 6000 sends a short packet and gets turned down. I'm sorry that I can't tell you how to change your card's packet type. It has something to do with configuring for et0 instead of en0, although netstat still shows en0 (isn't life great?). -John P. Eisenmenger Dept of Electrical Engineering Duke University
wohler@sapwdf.UUCP (Bill Wohler) (01/14/91)
[i wrote this several months ago before we allowed news to be posted. i am posting it now because others may be interested to know that our problem disappeared by simply reinstalling unix! in fact, i even have the automounter working flawlessly. (i must have done something different than the original installer.) however, i am still curious why our network was unreachable with the device et0 though. --bw] david@phys.anu.oz writes: >> # mount rsphy1:/users /mnt >> mount: server rsphy1 not responding: RPC: Authentication error; why = >> Invalid client credential ... jpe@egr.duke.edu (John P. Eisenmenger) writes: >The problem is in the type of ethernet packet in use. Your RS6000 is using >Xerox Ethernet, whereas you Ultrix station is using IEEE 802.3. If you >change your RS6000 to use IEEE 802.3 things will work. For some reason >this doesn't show up in other protocols, and most of the mounting process >actually goes okay. my machine suffers from the above problem as well. it was easy to change the ethernet device with smit (ha ha) to et0. afterwards the network was completely unreachable. changing the mtu on en0 to 1492 also had the same effect. further ideas are appreciated. the funny thing is that these mounts *succeed* at boot time (ie. from the mount all command in /etc/rc). however, root cannot access any files mounted via nfs. --bw wohler@sap-ag.de