IBM Support

Getting Started with IBM i NetServer

Troubleshooting


Problem

This document explains how to get started using IBM i Support for Windows Network Neighborhood (IBM i NetServer).

Resolving The Problem

This document explains how to get started using IBM i Support for Windows Network Neighborhood (IBM i NetServer).

The IBM i Support for Windows Network Neighborhood (IBM i NetServer) allows personal computers running Windows or Linux to seamlessly access integrated file systems directories and output queues on the IBM i system. This support does not require any additional software to be loaded on the personal computer. It takes advantage of the native file and print sharing protocol delivered with Microsoft Windows and the Linux Samba client. It does not require any software on the IBM i other than the IBM i base operating system. The only prerequisites for this support are that the IBM i and the personal computer be configured with TCP/IP and that the file sharing protocol on the personal computer be configured to use TCP/IP. Any data available through the operating system integrated file system (including stream files and CD-ROM) and any output queues (printers) on the operating system can be shared with the network by the IBM i administrator.

Although many OS/400 versions are mentioned in this document, several are mentioned for historical purposes only. Currently supported versions, at the time of current editing (26 May 2016) are V7R1 and above. Currently supported versions are subject to change.

Note: The Fastpath Setup assumes that System i Navigator and it's Network and File Systems functions are installed. Using Navigator to configure IBM i NetServer and shares is highly recommended. If this is not possible, then the GO NETS Command line Menu can be configured on the IBM i. Follow the directions on the following website to configure GO NETS:

http://www-03.ibm.com/systems/power/software/i/netserver/gonets.html

Command line APIs can also be used for NetServer configuration. Fastpath Setup instructions using the operating system command line APIs are available at the following Web site:

Fast Path to Setting Up IBM i NetServer:

http://www-03.ibm.com/systems/power/software/i/netserver/fastpath.html

    • - IBM i Setup



      TCP/IP Support: Verify that TCP/IP support has been configured on the IBM i. At least one external TCP/IP interface must be configured and active in order to use the NetServer.

      Use the Configure TCP/IP (CFGTCP) command to check and/or modify interfaces, routes, set up host table and domain name services, and so on. Once the configuration is complete, use the Start TCP/IP (STRTCP) command to activate the support.

      QSERVER Subsystem: The QSERVER subsystem should be started automatically. Confirm that it is started using the Work with Subsystems (WRKSBS) command. If the QSERVER subsystem is not started, use the Start Subsystem (STRSBS QSERVER) command to start it.

      Note: When working with NetServer properties, the property GUI tabs and options will vary depending on the versions of both the System i Navigator and the IBM i OS. Therefore, location of these functions on the GUI properties screen is not guaranteed.

      NetServer Name and Domain: Verify that the NetServer server name is unique on the network and that the NetServer is in the same PC domain (or workgroup) as the majority of the clients accessing the operating system file and print services. This will ensure that there is a PC Master Browser available in the PC domain to pass on announcement broadcasts from the NetServer (should you choose to have NetServer send them). This plays a part in allowing the NetServer to show up in Windows Network Places (if the Windows Network is properly configured to have it do so).

      You must have *IOSYSCFG authority to modify any part of the IBM i NetServer configuration. To change the NetServer default server and domain name, do the following:

      1.Open the System i Navigator and click the + sign next to the operating system system.
      2.Click the + sign next to Network.
      3.Click the + sign next to Servers.
      4.Click on TCP/IP.
      5.Right-click on i5/OS NetServer and click Properties from the pop-up menu.
      6.From this interface, you can change the NetServer name, the domain it is a part of, and the text description for the server.

      NetServer Guest User Profile: The option to configure a Guest profile is found on the Security Tab of the NetServer Properties. Guest support is needed for those NetServer users requiring only file and print sharing support that do not have an operating system user profile. If this field is blank, unknown users do not have access to operating system resources through the IBM i NetServer. *IOSYSCFG and *SECADM authority are required to modify NetServer guest support.

      Note: A Guest User Profile must have no special authorities. A password will be required if the Guest User Profile will be used for print sharing, however it is recommended that it not be given a password if it is to be used exclusively for file sharing. NetServer does not automatically configure guest support so users without IBM i user profiles cannot, by default, access NetServer.

      Starting and Ending NetServer: Any configuration changes made to the NetServer, with the exception of share and session administration, do not take effect until the next restart of the server. To stop and restart the NetServer from within System i Navigator, do the following:
      1.Open the system in System i Navigator.
      2.Expand Network and Servers and select TCP.
      3.Right-click on i5/OS NetServer and click Stop from the pop-up menu.
      4.Right-click on i5/OS NetServer again and click Reset and start from the pop-up menu.
      To stop and restart the NetServer from the IBM i 5250 emulation session, do the following:

      1. ENDTCPSVR *NETSVR and press <Enter>

      2. STRTCPSVR *NETSVR and press <Enter>

      To determine if the NetServer was started successfully do a DSPMSG QSYSOPR and check for CPIB680 - IBM iSupport for Windows Network Neighborhood (IBM i NetServer) initialization complete. If NetServer failed to start it will also send a message (usually CPIB683 or CPIB687) which will include a reason code and return code that indicate the cause of the failure.

      Determining if NetServer is Running: Use the Work with Active Job command to verify there is a QZLSSERVER job running under the QSERVER subsystem.

      WRKACTJOB SBS(QSERVER) JOB(QZLSSERVER)

      If the QZLSSERVER job is not active, then NetServer is not active and must be started, using one of the options above.

      Using the Work with TCP/IP Network Status (NETSTAT *CNN) command, the following entries are shown. If these connections are not displayed, start NetServer again.

      * * netbios > 001:27:44 Listen Port 137 name lookup
      * * netbios > 000:00:01 *UDP Port 137 name lookup
      * * netbios > 000:00:00 *UDP Port 138 name broadcast
      * * netbios > 000:30:57 Listen Port 139 Sessions
      * * cifs > 001:44:23 Listen Port 445 Sessions (used by V5R1 and later)

      Note: For NetServer access through a firewall the ports above will also need to be opened in the firewall.

      Starting NetServer Print Support: For NetServer print shares to function properly, the Network Print Server (NPS) must be started.

      To determine the status of NPS on a V4R4M0 or higher system, on the operating system command line type the following:

      WRKACTJOB SBS(QSYSWRK) JOB(QNP*)

      Press the Enter key. Ensure that there is a QNPSERVD job active (Daemon job). If there is no QNPSERVD job, start NPS with the following operating system command:

      STRHOSTSVR *NETPRT

      To check the prestart jobs for the NPS, on the operating system command line type the following:

      WRKACTJOB SBS(QUSRWRK) JOB(QNP*)

      Press the Enter key and then press F14 to include the prestart jobs. There should be at least one QNPSERVS job in a PSRW state. If there are no QNPSERVS jobs then you must start them. On the operating system command line, type the following:

      STRPJ SBS(QUSRWRK) PGM(QSYS/QNPSERVS)

      Press the Enter key.

      • - PC Setup



        Versions of Windows currently supported by Microsoft and the Linux Samba client can be used to access IBM i NetServer. Windows 95/98/ME/NT/2000/XP and Windows for Workgroups can also be used but are not currently supported operating systems.

        Windows Networking Support, Windows 98: From the Windows Start button select Settings/Control Panel/Network/Configuration. On the Configuration tab verify that Client for Microsoft Networks and TCP/IP are installed. On the Identification tab verify that Computer Name is a unique name on the network and that the Workgroup name is valid (preferably this should be the same as the NetServer domain name).

        Windows Networking Support, Windows 2000: From the Windows Start button select Settings/Network and Dial-up Connections/Local Area Connections. On the General tab verify that Client for Microsoft Networks and TCP/IP are installed.

        Check TCP/IP Support: Test the support by PINGing the IBM i system from a DOS command prompt as follows:

        PING IBM-i-NetServer-server-name

        All currently supported versions of Windows have Client for Microsoft Networks and TCP/IP installed by default.

        Resolving NetServer Name: Add an entry for the IBM i NetServer to a Domain Name Server (DNS), the local LMHOSTS for the PC, or set up a Windows Internet Name Server (WINS) to resolve the NetServer server name. The quickest way is to add an entry to the LMHOSTS file located in the \Windows directory on a Windows 95 PC, the \WINNT\system32\drivers\etc directory on a Windows NT PC, or the \Windows\system32\drivers\etc directory on a Win XP (or above) PC. If you cannot find an LMHOSTS file in the specified directory, it might not have been created yet. Rename LMHOSTS.SAM in that same directory to LMHOSTS, and add a line with the following format:

        TCP/IP-address IBM-i-NetServer-server-name

        For example: 9.5.10.1 QNETSERVER

        Finding the IBM i NetServer and Shared Resources: NetServer might also appear in the Windows Network Neighborhood (Network Places); however, this depends on the network TCP/IP configuration. Find Computer or Search for Computer (depending on the Windows operating system) is more likely to work in all environments.

        To display NetServer shares, double-click on the IBM i NetServer accessed through Find or Search for Computer or through Windows Network Neighborhood (also known as My Network Places). Windows Network Neighborhood is also available through Windows Explorer so NetServer shares can also be explored.

        Installing IBM i Access for Windows: Use the System i NetServer to install IBM i Access for Windows (known as Client Access Express, or iSeries Access on earlier releases) on your Windows PC. Administrating NetServer from a PC requires the use of System i Navigator. NetServer automatically shares the QIBM directory with clients for the purpose of allowing operating system users who already have user profiles, to install i Access for Windows on client PCs.


      • - iSeries NetSever Q&A



        Question:

        What exit points can be used to monitor IBM i NetServer activity and further control access to my IBM i?

        Answer:

        The exit points used by the AS/400 NetServer are the same as the exit points for the optimized file server and optimized network print server functions including the following:

        QIBM_QPWFS_FILE_SERVExit point for file shares
        QIBM_QNPS_ENTRYExit point called at print share server initialization
        QIBM_QNPS_SPLFExit point called to process spooled file output

        They are documented in detail in the IBM i Knowledge Center.

        To visit the V6R1 Knowledge Center, click HERE now.
        To visit the V7R1 Knowledge Center, click HERE now.
        To visit the V7R2 Knowledge Center, click HERE now
        To visit the V7R3 Knowledge Center, click HERE now

        In the Knowledge Centers, search for the specific exit point name.


        Question:

        What are the default NetServer settings?

        Answer:

        The default settings include the following:
        oThe IBM i NetServer name is Q + the system name.
        oNetServer is started with TCP/IP (STRTCPSVR *NETSVR)
        oThe QIBM directory, which contains the source code for the i Access for Windows PC Clients, is shared by default. Additional default shares may be configured based on licensed program options installed on the system.
        Question:

        Where can I get information on PTFs available for IBM i NetServer?

        Answer:

        See the following Web site for the 'Get Current' PTF listing for V7R1/V7R2/V7R3 IBM i NetServer:

        http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes

        Question:

        Where can I get additional setup and troubleshooting information for IBM i NetServer?

        Answer:
        Support information for NetServer is available at the following location: http://www-03.ibm.com/systems/i/software/netserver/index.html. This page contains the fast path setup, documentation, troubleshooting tips, and so on.

        A list of basic documents is available in IBM Technote N1019558, Introduction to IBM i NetServer Documents. Click HERE to view N1019558 now.

        Many other IBM Technotes are available in the online Knowledgebase at http://www-912.ibm.com/s_dir/slkbase.nsf/slkbase .
        [{"Product":{"code":"SWG60","label":"IBM i"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Host Servers","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"4.5.0;5.1.0;5.2.0;5.3.0;5.4.0","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

        Historical Number

        11600129


      Document Information

      More support for:
      IBM i

      Software version:
      4.5.0, 5.1.0, 5.2.0, 5.3.0, 5.4.0

      Operating system(s):
      IBM i

      Document number:
      644841

      Modified date:
      18 December 2019

      UID

      nas8N1019708

      Manage My Notification Subscriptions

      Page Feedback