As I recall, this usually comes up when you do not have write authority
to a share. First, check that the share is NOT read-only. This article
has some other suggestions that you may want to review.
http://www.itjungle.com/mgo/mgo111903-story02.html
-Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
tim.dclinc@xxxxxxxxx
Sent: Monday, February 08, 2010 5:21 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: qntc and authority
Sure...
Error: CPFA09C Not authorized to object. Object
is/qntc/10.0.0.99/FSBackup.
iSeries Version v5r4
PC: Windows 2008 Standard Service Pack 1 64bit.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Monday, February 08, 2010 5:44 PM
To: Midrange Systems Technical Discussion
Subject: RE: qntc and authority
Well, that depends...
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?
midrange.com
