Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Microsoft SFU and NFS 3.0

0 views
Skip to first unread message

dave....@pmic.com

unread,
Nov 5, 2003, 9:01:51 AM11/5/03
to
I am trying to import a Microsoft share to my main Novell server. The MS
box is a W2K box running Services for Unix, which allows it export a share
as a unix drive. My novell box is 5.1 sp6 running eDir 8.6.2 and NFS 3.0
sp5. I can mount the volume just fine. The issues come up when I try and
create a file or folder. Typically they come up as read only. If I try to
change the name of the folder, the volume will dismount and occasionally
abend the server. Any suggestions? This kluge has come about because the
users do not want to have their server (w2k) login to tne network to
mount/map a novell volume. A second question would be: Can I map/mount a
novell volume as a service?

Brad Doster

unread,
Nov 7, 2003, 9:08:38 AM11/7/03
to
In article <jp7qb.4425$5N5....@prv-forum2.provo.novell.com>, wrote:
> I am trying to import a Microsoft share to my main Novell server.
>
Well, it's a pretty good bet that this is not supported, but doing what we
can with it...

> The issues come up when I try and
> create a file or folder. Typically they come up as read only.
>

It seems there are several levels of permissions involved here: 1) the W2K
NTFS and/or share permissions, 2) The persmissions W2K publishes with the
NFS export, and finally, 3) the permissions that NetWare sees and
publishes. I would think that 1) and 2) affect 3), however I have no idea
how 1) and 2) are implemented -- I would guess the MS docs might help you
there?

> If I try to
> change the name of the folder, the volume will dismount and occasionally
> abend the server.
>

Ouch... and again, probably unsupported, so I don't know how much help
there is for it.

> This kluge has come about because the
> users do not want to have their server (w2k) login to tne network to
> mount/map a novell volume.
>

You lost me there. From what you've described it sounds like you want to
make the W2K volume available to NetWare clients, presumably running
Windows? If yes, then why not just map to the W2K server using the MS
Client for MS networks? Maybe a better explanation of the problem and goal
would lead to a different/better solution...

bd
NSC Volunteer SysOp
www.InsightNetSolutions.net

0 new messages