Can't get Windows 10 to connect to iSCSI target

[Bryan R.]

Well, I was about to post this problem I've been having but I just found a Reddit post that solved it perfectly. Perhaps it is a common problem but not many people utilize iSCSI in W10. 
Fix from Reddit:

Quote

The fix is simple: Go into your device manager and go to the Storage Controllers section. You'll probably see an Unknown Device there (this is the failed iSCSI driver). Open the device and attempt to manually update the driver, choosing Browse My Computer For Driver Software, and then Let Me Pick Which Drivers To Install. The Microsoft iSCSI Initiator will probably be the only one available. Just install that one, restart your Microsoft iSCSI Initiator service, and Bob's your uncle.

Spoiler

 

I'm working on a little home project. I have two boxes, one runs Server 2016 with 7 drives in a storage pool and is hosting a few iSCSI targets. The second is my main PC and runs Windows 10. I can't seem to get my Windows 10 machine to see the iSCSI targets in Server 2016.

 

The server itself can connect to the targets, just not the remote PC. 

 

I've checked the firewalls on each machine. The W10 has a rule for iSCSI Service enabled. The Server 2016 has iSCSI Service, iSCSI Target, and iSCSI Target Service enabled. I found this article: Configuring Windows Firewall for iSCSI Software Target. All those ports are already enabled on the server through File Sharing and Network Discovery rules. The programs listed in that article don't exist on the client or server machines so it's probably outdated info from 2009.

 

I've tried turning off the firewall on both ends.

 

I've also added a rule that should have allowed all traffic to and from the local network on each end.

 

I'm not sure what else to check... Please advice, thank you!

 

 

So after banging my head against the wall, it was that simple.

 

Now I will get to see the performance of running VMs in this configuration.