×
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.
QNTC normally uses the current job user (and its associated password
hash value) to negotiate access to servers via QNTC. The problem we're
having these days relates to Microsoft Server 2008 r2, which changes the
"password hash" defaults to methods that are not available on IBM i.
QNTC tries to authenticate with NTLM or NTLMSSP, which are part of CIFS
standard for internet security. New MS servers disable NTLM, in favor
of NTLMv2, which is not in CIFS specification, and therefore not part of
IBM's Netserver product.
Can you give us more information, such as what error messages you see,
OS version, OS of the server you are accessing via QNTC, and so forth.
Thanks,
-Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
tim.dclinc@xxxxxxxxx
Sent: Monday, February 08, 2010 4:24 PM
To: midrange-l@xxxxxxxxxxxx
Subject: qntc and authority
When using the MD command to create a directory in qntc, how is the
authority done between the iseries and the windows network?
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
