× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



RTF-Archives :-)

Regards,


Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com

------------------------------

message: 4
date: Fri, 20 May 2016 14:33:58 -0500
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: Consuming (mounting) over a Windows NFS share from IBM i

Hi Rob


RJS Software had knowledge base articles on this - might still be
available, or Richard will chime in.


I think one of the main issues is getting access using GIDs in the user
profile and in the NFS server setup in Windows.


Good luck!

Vern


On 5/20/2016 2:03 PM, Rob Berendt wrote:
I would like to avoid using /QNTC to access Windows shares. I've had too
many strange issues based on things like length of share names, etc.

I want to serve up a share on Windows using NFS.
I then want IBM i to MOUNT over that share.

I've done this between lpars of IBM i.
I've used EXPORTFS on one lpar and MOUNTed from another.

I'm sure that someone on this list has done so. I am hoping that someone
has some step-by-step instructions for both the Windows side, and the IBM
i side.

A system running under user QPGMR will be accessing this share.
Vendor software (GoAnywhere MFT by Linoma).
Internet - - > DMZ IBM i - - - - > Windows (Intranet)
https: - - - > GoAnywhere - - - > NFS Export


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.