_______________________________________________________________
Document Information
| Document Number: | 14944413 |
| Functional Area: | Integrated File System |
| Subfunctional Area: | QNTC |
| Sub-Subfunctional Area: | General |
| OS/400 Release: | V5R3M0; V5R4M0; V6R1M0 |
| Product: | I5/OS (5761SS100) OS/400 BASE (5722SS100) |
| Product Release: | N/A |
_______________________________________________________________
Document Title
Configuration of QNTC (SMB Client) File System
Document Description
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: http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes |
| 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 Server that you are attempting to access, you can obtain assistance under a consulting agreement. |
| 3 | Ensure the Windows server and Domain names are 15 characters or less in length. |
| 4 | Ensure that all Windows based shares are 12 characters or less in length. This is a permanent restriction as it causes the Windows server to return a 3406 error code from the SMB transaction. |
| 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 server. Also ensure that the user IDs have authority to access the shares on the Windows server. Notes: a. Authority to the shares can only be administered from the Windows server. b. 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 server on the Integrated Server 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 www.microsoft.com) 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 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 a Integrated 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 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 the Windows Server) that has the proper authorities to the specific shares to be accessed on the Windows 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 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. |
__________________________________________________________________
PMR Number: |  | |
Related APARs: | | |
Related Public Documents: | | |
- IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information.