iScsiPrt errors 129, 39, 27 can 9 indicate that the Repository is not reachable (4032869)

After reviewing the Windows System Log to troubleshoot repository issues, reveals iScsiPrt Error Events 129, 39, 27 and 9.  These errors indicate that the Initiator send either a management command or an initiator task to the target and did not receive a reply.

Resolution:

Provision a second NIC, either physical or virtual,  to handle the iScsi traffic

• Enable only "TCP/IPv4" in the NIC's properties window
• Click the "Advanced" button and uncheck "Register this connection's address in DNS"

• Close this dialogue window

• With the NIC properties window open, click "Configure"

• Change Jumbo Packets to 9014 bytes
• Set the following settings to DISABLED:
• IPv4 Checksum offload
• Large Send Offload
• TCP Checksum Offload
• UDP Checksum Offload

• Close all dialogue windows

Open an elevated PowerShell prompt

• Type the following commands:
• Netsh int tcp set global RSS=Disabled 
• Netsh int tcp set global chimney=Disabled 
• Netsh int tcp set global autotuninglevel=Disabled 
• Netsh int tcp set global congestionprovider=None 
• Netsh int tcp set global ecncapability=Disabled 
• Netsh int ip set global taskoffload=disabled 
• Netsh int tcp set global timestamps=Disabled 
• Close PowerShell

• Create a new connection with:
  • Microsoft iSCSI Initiator Adapter
  • Enter the IP address of your iScsi connected storage

• Click Save
• Open the "Favorite Targets" tab
  • Remove the initiator from this list
• Click OK

You now have an ISCS NIC provisioned with Microsoft best practices.