From: "Michael French" <mfrench@ashevillemail.com>
To: linux-admin@vger.kernel.org
Subject: Slightly off topic NFS question
Date: Thu, 20 Mar 2003 09:18:22 -0800 [thread overview]
Message-ID: <001d01c2ef04$b6374ba0$0500a8c0@castor> (raw)
Don't ask why, but I have to get a Windows box and a Solaris box talking
over NFS. The win box is the server and solaris box is the client. I
installed the Services for Unix on the Win box and configured NFS (what
little there is to do). I created a share and thought I was ready to rock.
I do a showmount -e on the Win box and the share shows up. rpcinfo
servername shows all the processes I expect.
From the Solaris client, I can do the same thing with rpcinfo and
showmount -e servername and get results back. I had the firewall admin open
up all IP traffic between these to boxes (just for now, for testing, having
problems before this with just 2049 and 111 open). I can mount the share
with no problem (mount -o rw -F nfs 192.168.0.10:/testmount /testmount). It
mounts right away and running mount shows it with read/write/setuid on
server, but as soon as I try to write to the share, I get a "Stale NFS"
error. I check the permissions on the mounted folder, changed to 777 before
I mounted, owned by nobody/nobody (I am root right now). On the win server,
the log is showing a successfull mount, no errors. The permissions on the
directory on the server are wide open for all users, including connecting
NFS clients. Any idea what the hell could be going on?
I am using Solaris 8 and Win2K with SFU 2.2. Win2K patched to SP3.
Thanks for any answers peope might be able to provide, I have to get this
working today.
Michael French
next reply other threads:[~2003-03-20 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 17:18 Michael French [this message]
2003-03-20 19:10 ` Slightly off topic NFS question Paul Furness
2003-03-21 2:47 ` Michael French
2003-03-21 2:58 ` gateway problem San
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001d01c2ef04$b6374ba0$0500a8c0@castor' \
--to=mfrench@ashevillemail.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).