× 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.



After applying solution found in this IBM document, a mystery is solved.
A profile on our V5R4 machine, created back in 2005, is finally able to
connect to network servers with WRKLNK and CPYTOIMPF.

This is a happy day.
Eric

IBM Software Technical Document

Document Number: 578612192
____________________________________________________________
Functional Area: Integrated File System
SubFunctional Area: QNTC
SubSubFunctional Area: General
____________________________________________________________
Product: I5/OS (5761SS100); IBM I (5770SS100); OS/400 BASE (5722SS100)
Release: 5.4.5; 6.1; 6.1.1; 7.1; V5R4M0; V5R4M5; V6R1M0; V6R1M1;
V7R1M0


Keywords: QNTC, SMB Client
____________________________________________________________
Document Title:QNTC Required Change for Accessing Windows 2008/2008 R2
Servers
Document Description:
The following
Windows Policy Settings will need to be changed to allow R540 client to
authenticate to the Windows Server 2008/2008 R2 or Windows 2008/2008 R2
AD Level:

"Network Security: Do not Store LANMAN hash on next password change" New
Value = Disabled:
"Network Security: LAN Manager Authentication level" New Value Send LM &
NTLM - use

After the changes are saved, the user profiles passwords will need to be
reset to allow the LANMAN Hash to be generated. Note with the
Application of the PTFs for R610 and R710, these changes are not
required. The PTFs enable the NTLMv2 support.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.