The issue has been resolved. I'm not sure if this is the case, but I would surmise that you cannot have multiple initiators all communicating with the same port. When I allowed the Win2k16 initiator to communicate on another port, the issue went away.
Windows Server2016 iSCSI connectivity problems
Hello Everyone,
I'm having an issue with my Windows Server 2016 initiator connecting to my TrueNAS 12 target.
The server connects randomly, and then loses connection when the TrueNAS server reboots. I get the following errors:
iSCSIprt Event ID 1
iSCSIprt Event ID 70
MSiSCSI Event 113
I've tried rebooting the Win2k16 server, restarting all iSCSI services, deleting all target records from the iSCSI initiator properties, and re-adding them.
Oddly, I have a Win2k12r2 that's acting as an initator as well, which has no issues connecting to the TrueNAS target, and re-establishing connectivity when the TrueNAS target reboots.
2 additional answers
Sort by: Most helpful
-
Marco Schiavon 76 Reputation points
2021-09-19T09:49:50.673+00:00 have you try to
- disable stp on the ports of iscsi
- enable flow control on all iscsi ports
- disable speed auto negotiation on all iscsi ports
- update servers nic drivers and firmware
last
remove any kind of NLB on server sideMarco
-
Limitless Technology 39,391 Reputation points
2021-09-20T18:56:53.683+00:00 Hello @Sameer Sheikh
I would like to suggest you to check below Troubleshooting steps.
- Please check from the network firewall or Windows firewall if the 3268 iSCSI port and ip is not blocked.
- Please check from the NAS if the server Name or ip is added to Mapping list.
- Please try to disable Windows firewall and Antivirus for temporary to narrow down this issue.
If the reply was helpful, please don’t forget to upvote or accept as answer.