IBM Power Connect, learn, share, and engage with IBMPower. Join / Log in
Hello,according to IBM support (https://www.ibm.com/support/pages/ibm-i-netserver) windows 2016 and 2019 servers are not supported for network sharingThe steps to follow to make the network share work on the 2016 and 2019 servers:Step 1: Checking the version of the SMB protocol used by NetServer on your AS400 machinego to your machine as400 and run the following command CALL PGM(QZLSMAINT) PARM('40''0')WRKSPLF5 QPCSMPRTRID LIC LOG ENTRY ID 010004DC TYPE 4400 (SERVER MSG BLK ) F001 NOTE SIZE 0068 REQUESTER TDE:B000200008 162000 NAME:SK-ASC010P LINKREG:RID ZLS EXTENSION FLAGS DUMP FOR ENTRY ID 010004DC TYPE 4400 (SERVER MSG BLK ) F001 DUMP SIZE 0000E6OLD FLAGS 0000000000000000 NEW FLAGS 0000000000000000 ****** END OF DUMP ****** There are 5 possible values related to SMB usage:0000000000000000 - Protocol version is negotiated and defaults for the OS version will be used (SMBv1 for 7.2, SMBv2 for 7.3, SMBv3 for 7.4)0000000000000080 - Allows SMBv1 only0000000000000100 - Disables SMBv10000000000000400 - Enables SMBv2 for 7.2 (7.3 and later do this by default)0000000000000500 - Combination of x100 and x400. Allow SMBv2 and higher only (Note: has the same effect as 0x100 for 7.3 and later)Note: 7.2 provides support for SMBv1 and SMBv2. 7.3 provides support for SMBv1 and SMBv2. 7.4 provides support for SMBv1, SMBv2, and SMBv3. 7.1 and earlier versions only support SMBv1 (so these flags have no impact or meaning for those releases)Step 2: Check the SMB version activated on the 2016 or 2019 server Go to your windows machineLaunch PowerShell from started menu# To display which version of SMB protocol installed Get-WindowsOptionalFeature –Online –FeatureName SMB2ProtocolGet-WindowsOptionalFeature –Online –FeatureName SMB1Protocol# To display which of SMB protocol is enabledsc.exe qc lanmanworkstation# another way to see which SMB version is runningsc.exe query mrxsmb10sc.exe query mrxsmb20===> Example: if your machine code LIC as400 is in version 7.3 you must have SMBv2 activatedStep 3: network verification and Local Group Policy 3-1 the local port on the as400 machine must be listening: commande : NETSTAT *CNN + F14 Note:Port 445, Newer versions of SMB (post Windows 2000) started to use port 445 on a TCP stack. The use of TCP allows SMB to work over the Internet.3-2 Check on the windows machine that no IPSec policy is blocking TCP port 445 by using the following command:commande DOS: Netsh ipsec static show policy all ERR IPsec[05072] : No Policies in Policy Store 3-3 if all the steps are checked and the network share does not work then edit the Group Policy Editor file:Open the Local Group Policy Editor (gpedit.msc).In the console tree, select Computer Configuration> Administrative Templates> Network> Lanman Workstation.For this setting, right-click Enable insecure guest connections and select Edit.Select active and OK3-4 also check the entries in the Host file C:\Windows\System32\drivers\etcbest regardsBrahim AIT OUGRAM