Here's how I understand the current state of QNTC...

IBM Netserver on OS prior to V6R1 will only support the use of LM or NTLM (v1) for client authentication. Windows products (since Vista) have changed the default policies regarding the use of LM / NTLM (v1), so that this protocol is disabled by default. Enabling NTLM support on the Windows server corrects the authentication issue, but many security scanning products will flag this as a problem...

IBM has a PTF for 6.1 that enables NTLMv2 authentication for client access through QNTC.

-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Wednesday, May 18, 2011 10:22 AM
To: Midrange Systems Technical Discussion
Subject: RE: QNTC access gets CPE3401 to one server.

Chris wrote:

We have always had issue access QNTC.
We have tried several options and none worked.
We use programs that run under Owner Authority and
the Owner has a local profile on the windows server.
We just restrict access to the iSeries program that accesses the windows

Similar to our experience and use.
One possible difference is use of QNTC for data access between System i,
in addition to Windows.
Typical example is jobs and program calls to process data on one server
to update data on another.
We maintain "standard" profiles on these servers to support QNTC, and try
limit person-specific profiles to MS AD and the required
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


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

This mailing list archive is Copyright 1997-2019 by 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].