Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!jik From: jik@athena.mit.edu (Jonathan I. Kamens) Newsgroups: comp.unix.questions Subject: Re: NFS between het. platforms (sun and chromatics) Message-ID: <1991Mar22.174047.13067@athena.mit.edu> Date: 22 Mar 91 17:40:47 GMT References: Sender: news@athena.mit.edu (News system) Distribution: comp Organization: Massachusetts Institute of Technology Lines: 28 I've seen two different things that cause the "Invalid client credential" error you mentioned. The first is that the host making the mount request is not putting a FDQN into the "host" field in the request structure that rpc.mountd sees, and it's in a different domain or something so rpc.mountd can't do a gethostbyname() on the name and end up with the same IP address as the message indicates that it's coming from. The second (if I recall correctly) is a line starting with a space in /etc/hosts on the machine from which you're trying to mount. Such a line caused the nameserver library code (on an Ultrix machine) to mess up and misresolve the host name of the client making the mount request, leading to the problem described above. When you figure out the problem, I'd be interested in knowing what it was, if it was something other than these two possibilities or what kepowers@mbunix.mitre.org suggested (importing the filesystem secure). Please post what you find. Good luck! -- Jonathan Kamens USnail: MIT Project Athena 11 Ashford Terrace jik@Athena.MIT.EDU Allston, MA 02134 Office: 617-253-8085 Home: 617-782-0710