linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael French" <mfrench@ashevillemail.com>
To: Paul Furness <paul.furness@vil.ite.mee.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Slightly off topic NFS question
Date: Thu, 20 Mar 2003 18:47:55 -0800	[thread overview]
Message-ID: <000701c2ef54$48409ac0$0500a8c0@castor> (raw)
In-Reply-To: 1048187418.24414.106.camel@Zebra.vil.ite.mee.com

    Thanks for the tips Paul, unforntunately I had no luck in making this
work.  I am pretty sure it's an authentication issue, but I did have more
time to try and set the relationship with the MS SFU and the Unix client(s).
I dug around the net a little more and found a package called ProNFS which
works great.  I downloaded it, installed it, and had it running within 5
minutes.  Simple as can be, you select the directory you want to share,
assign users who can access it and set the access levels, all done on the
fly.  I was able to mount and copy files immediately.  Don't waste your time
with Services for Unix unless you have a week or two to play with it, the
instructions are horrible and the interface is completely non-intutive.

Michael French

----- Original Message -----
From: "Paul Furness" <paul.furness@vil.ite.mee.com>
To: "Michael French" <mfrench@ashevillemail.com>
Cc: <linux-admin@vger.kernel.org>
Sent: Thursday, March 20, 2003 11:10 AM
Subject: Re: Slightly off topic NFS question


> I'm afraid I can't give you a complete answer, just some pointers.
> Unfortunately, I haven't used NFS server from a windows machine, so
> these might be completely the wrong track. Anyway...
>
> I have had problems getting samba to mount windows shares in the past,
> and it seems likely that windows NFS uses some of the same auth
> mechanism. The main problem I had was that, if you tried to mount the
> windows share as a user that didn't exist _on the windows box itself_ it
> wouldn't let you mount, even if perms were open to everyone.
>
> As for the stale NFS handle, I have had similar problems with NFS in the
> recent past. I spent ages trying to figure it out, and in the end it was
> simply that I had to be someone other than root.
>
> The other thing that helped was to make the exported file system use
> no_root_squash.
>
> Finally, you could always try the "Microsoft Solution" and reboot both
> the Windows machine and the Solaris box. I've had that work before for
> this kind of thing, too.
>
> Sorry I can't be more directly helpful.
>
> Paul.
>
>
> On Thu, 2003-03-20 at 17:18, Michael French wrote:
> >     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
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin"
in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> Paul Furness
>
> Systems Manager
> Visual Information Lab
> Mitsubsihi Electric ITE BV
> Guildford, UK
>  __________________________________________________________
> |  Fight Spam! Join EuroCAUCE: http://www.euro.cauce.org/  |
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>


  reply	other threads:[~2003-03-21  2:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 17:18 Slightly off topic NFS question Michael French
2003-03-20 19:10 ` Paul Furness
2003-03-21  2:47   ` Michael French [this message]
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='000701c2ef54$48409ac0$0500a8c0@castor' \
    --to=mfrench@ashevillemail.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=paul.furness@vil.ite.mee.com \
    /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).