Issues:
1. IBM Netserver relies on WINS to build its list of available network shares. WINS is being disabled in most networks, due to security concerns. Without WINS, you are responsible for populating share names manually. We wrote a program to add server links to QNTC as part of our startup program, which works fine, but requires dilligence to maintain.
2. IBM netserver conforms to CIFS standards, but Microsoft found these standards dificient, and abandoned the restrictions of CIFS, as implemented by IBM on i. Newer versions of Windows prefer stronger security schemas, and disable the encryption protocols used by IBM Netserver. I think there are some recent patches for IBM i OS that enable stronger encryption, but I haven't studied them.
Other concerns:
PCI and other security driven intrusions are forcing many security concerns onto the IBM i Admins, to eliminate unencrypted access to data. I believe this is of concern as Netserver uses the SMB protocol, which I believe transmits the accessed data across the network without encryption. I'm not certain if NFS is in any way protected from this issue, so I cannot say more...
-Eric (on vacation) DeLong
________________________________
From: midrange-l-bounces@xxxxxxxxxxxx on behalf of sjl
Sent: Thu 8/12/2010 9:59 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Using QNTC
All -
After reading through the archives about issues and concerns with using the
QNTC file system to copy files to/from a Windows server, I fully understand
that NFS is better and more stable.
However, given that:
1) There is an incredible bureaucracy within our multinational company to
get the necessary approvals that must be done to install NFS on the Windows
Server (if not already installed)
and
2) Other production applications on our systems are already using QNTC to
copy files to/from Windows servers
I need to know about any potential gotcha's beyond the necessity of putting
a MKDIR '/QNTC/Servername' in the system startup program to ensure that the
server name remains mapped after an IPL.
Regards,
sjl
--
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.
midrange.com
