Hallo Zusammen,
es gabe einen Wrkaround, welcher aber nicht mehr zugänglich ist, aber vielleicht hat ihn noch jemand:

With QNTC, any OS/400 program that would normally access stream file data in the IFS can be rewritten to access data on a Windows NT or 2000 server. You can also use QNTC to access data on a Windows 2003 server with Active Directory installed, but it may require you to make a configuration change on the 2003 server. IBM reports that the digital signature feature of the Server Message Block (SMB) protocol on 2003 servers affects OS/400's ability to use WRKLNK on these servers' shares or to back up 2003 server data by using the SAV command. IBM has posted a circumvention to this situation on its Web site.
http://www-1.ibm.com/servers/eserver...orkaround.html

Configuration of QNTC (SMB Client) File System
Technote

Configuration of QNTC (SMB Client) File System

1 Ensure all of the most recent IBM AS/400 NetServer™ or IBM iSeries™ NetServer™ and QNTC (SMB Client) File System PTFs have been applied.

For information on iSeries NetServer, refer to the following Web site:

http://www.as400.ibm.com/netserver

For a listing of AS/400 NetServer or iSeries NetServer PTFs, refer to the following Web site:

IBM System i Technical Support: Recommended fixes
2 Ensure AS/400 NetServer or iSeries NetServer is running and configured for the same domain as the Microsoft Windows NT Server.

Note: If the AS/400 NetServer or iSeries NetServer is not configured for the same domain as the Windows NT Server that you are attempting to access, you can obtain assistance under a consulting agreement.
3 Ensure the Windows NT server and Domain names are 15 characters or less in length.
4 Ensure that all Windows NT shares are 12 characters or less in length (refer to APAR SA88496). To link to SA88496 immediately, click here .
5 Ensure the user IDs that are to be used to access QNTC have the same password on the IBM System i™ products and the Windows NT server. Also ensure that the user IDs have authority to access the shares on the Windows NT server.

Notes:
a If you use QSECOFR, do not use it to initially access the QNTC file system (refer to APAR SA79203). To link to SA79203 immediately, click here .
b Authority to the shares can be administered only from the Windows NT console. Assistance with granting authority to shares can be obtained under a consulting agreement or by contacting Microsoft support.
6 Ensure that there is only one Master Browser in the subnet, or if the Windows NT server on the IPCS is the Primary Domain Controller, ensure that it is configured as the Master Browser and no other PC or server on the subnet is configured for this function. BROWMAN.EXE (part of the MS Resource Kit for Windows NT) or BROWSTAT.EXE (from Microsoft's subset to the Resource Kit available on Microsoft Corporation ) can be used to perform this function. Any assistance with debugging and/or configuring the Master Browser can be obtained under a consulting agreement or by contacting Microsoft Support.
7 (Optional) If you want, you can configure a WINS server but this is not necessary. However, if you have Windows NT Servers that are within the same domain but not in the local subnet and WINS is properly configured , these servers will also be displayed under the QNTC File System without intervention by the user. Any assistance with debugging and/or configuring a WINS server can be obtained under a consulting agreement or by contacting Microsoft Support.

Notes:
a It is not currently recommended that the Primary WINS server be configured on the Integrated PC server/IBM Integrated Netfinity Server due to the inherent difficulties in setting up WINS on multihomed server.
b AS/400 NetServer or iSeries NetServer must be configured to point to the WINS Server.
c All password and user ID requirements apply to all Servers.
8 (Optional) DNS Configuration. If you do not have a WINS Server you will only be able to access the server shares on an Windows NT Server outside of the local subnet using the MKDIR '/QNTC/<IP address>' or MKDIR '/QNTC/<NT Server name>' if you have a DNS that references the Windows NT server.

Notes:
a It is recommended that you configure WINS rather than using this method.
b Any access created through MKDIR is removed when the System i is IPLed and must be re-created manually.
c All servers must be in the same domain.
9 Ensure that the AS/400 NetServer or iSeries NetServer can be found through Start > Find computer. If you are able to find the AS/400 NetServer or iSeries NetServer through this method, the configuration on the System i is correct. This does not ensure that the AS/400 NetServer or iSeries NetServer resides within the same domain as the Windows NT Server.
10 Now sign on the System i with a user ID (usually with administrator authority on Windows NT) other than QSECOFR (until a PTF is available for SA79203) that has the proper authorities to the specific shares to be accessed on the Windows NT server and run WRKLNK QNTC . Type a 5 next to QNTC and press the Enter key. If you do not see the name of the Windows NT server, verify Steps 2, 3, 4, and 7. If you configure Steps 5 and 6, verify those steps also. If assistance is required with Steps 4, 5, and 6 (if the DNS is other than the System i DNS) you can refer to www.microsoft.com/support , call Microsoft Support, or we can assist under a consulting agreement.