RE: Mounting NFS file share -- MIDRANGE-L

Not safe to assume that - you don't need NetServer at all to use NFS- they have absolutely nothing to do with each other. As Scott said,NetServer enables Windows machines to see shares on an iSeries - QNTCis the reverse - enables an iSeries to see shares on Windowsmachines. Both use Samba.

NFS does not use Samba - has nothing to do with Windows as such - itcan also be used to connect to a Unix or Linux box. So it is moreversatile, and is also a much better performer.

So you should completely forget about NetServer and QNTC -concentrated on NFS. We have a couple knowledge base articles onconnecting to an NFS service on Windows if you are interested.Contact me at vern@xxxxxxxxxxxxxxx - no sales pitch, I promise!!


At 07:46 AM 12/13/2006, you wrote:

Thanks everyone.
I guess I wasn't entirely sure about the differences of the two. I
understand now. I did know I would need NFS running on the other server
in order to use to mount a *NFS file share. I didn't know the server
running Windows 2003 that I was trying to share with didn't have NFS
support.
Am I safe to assume that regardless of the differences I need NetServer
configured correctly in order to use either?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Wednesday, December 13, 2006 12:13 AM
To: Midrange Systems Technical Discussion
Subject: RE: Mounting NFS file share

Clarification noted - my point was that NFS has nothing to do with
Windows networking, which is implemented in NetServer and QNTC on
iSeries.

Reason I made the point is that the original poster seemed to be
putting NFS and QNTC together.

At 12:12 AM 12/13/2006, you wrote:


> > Just to be clear - NetServer - which uses /QNTC - is not related to
NFS,
> > except by accident of some similar names.
>
>Just to be clear about being clear :)   NetServer is the program that
lets
>Windows and Samba clients access the IFS on your System i.  NetServer
>makes your System i appear in "Network Neighborhood".  In other words,
>NetServer is the Windows Networking server for the System i.
>
>/QNTC is not NetServer.  It's "iSeries NetClient" (though they've
probably
>changed the name to "i5 NetClient" nowadays).
>
>/QNTC is the client-side that lets i5/OS access Windows and Samba
servers.
>NetServer is the server-side that lets Windows and Samba clients access
an
>i5/OS server.
>
>They are related, but they're opposites.  Just as Firefox is
>the opposite of an Apache server.
>
>/QNTC on the iSeries does read and use some of the configuration
settings
>that are configured in NetServer, and that might create the illusion
that
>they're the same thing, but they're not :)
>--
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
>To post a message email: MIDRANGE-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>or email: MIDRANGE-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.