In the past it was speed. Trying to browse the Windows server from QNTC was agonizingly slow. Even trying to copy a QTEMP file to the QNTC IFS folder was horribly slow. Sometimes the Windows server would just refuse the connection or stop in the middle of an operation and the file would never get completely written. FTP ended up being much faster and much more reliable so we went with FTP.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Saturday, February 17, 2018 11:01 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: QNTC to access Windows file server
What issues were you having?
I've been using QNTC successfully since the AS/400 days. For us, it worked fine then and still works fine now (if you're on 7.3 make sure you have all the QNTC recommended fixes if you use SMB2).
The only real hurdle I know about is with authentication. To authenticate you need either:
1. Matching users and passwords on both systems (no adopted authority allowed) 2. Kerberos
HTH
-----Original Message-----
From: Mike Cunningham [mailto:mike.cunningham@xxxxxxx]
Sent: Friday, February 16, 2018 6:30 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: QNTC to access Windows file server
Because of past issues with trying to mount a Windows file server under the IFS we decided to do all file transfers between our IBM i system and Windows systems using FTP. NFS seemed to be the preferred method for doing this some years ago but at the time our Windows admins were not too keen on adding NFS to the windows files servers. FTP works OK but always seemed to me like there should be a better way when all these servers are in the same data center and some even on the same network switch. We are now on V7.3 and Windows 2016 and wondering if there have been any improvements in this area that we could try.
Mike Cunningham
________________________________
This email may contain confidential information about a Pennsylvania College of Technology student. It is intended solely for the use of the recipient. This email may contain information that is considered an “educational record” subject to the protections of the Family Educational Rights and Privacy Act Regulations. The regulations may be found at 34 C.F.R. Part 99 for your reference. The recipient may only use or disclose the information in accordance with the requirements of the Federal Educational Rights and Privacy Act Regulations. If you have received this transmission in error, please notify the sender immediately and permanently delete the email.
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
________________________________
This email may contain confidential information about a Pennsylvania College of Technology student. It is intended solely for the use of the recipient. This email may contain information that is considered an “educational record” subject to the protections of the Family Educational Rights and Privacy Act Regulations. The regulations may be found at 34 C.F.R. Part 99 for your reference. The recipient may only use or disclose the information in accordance with the requirements of the Federal Educational Rights and Privacy Act Regulations. If you have received this transmission in error, please notify the sender immediately and permanently delete the email.
midrange.com
