iSCSI wizard unable to determine IQN for the Windows 10 client

[WhackyWakie]

Hi, I just setup a VMs lab using hyper-v. There are 2x DC, 1 iSCSI target and 1 initiator server, and 2 Windows 10 clients VMs, in a single AD (except for the hyper-V host). From the iSCSI storage server, I create iSCSI targets and add other VMs as initiators. While using the wizard to add the initiators I have no issue adding the hostname of servers via the “Query initiator computer for ID”, but it failed with Windows 10 with “unable to determine IQN for the client”. I used the "find" feature to get the hostname via the AD to make sure the name is correct.






Then from the Win10 client I started the initiator and query the iSCSI server, then the win10 client’s IQN appear in the iSCSI server wizard “Select from the initiator Cache on the target server:”. From the iSCSI server end I can select and add it as the initiator using the cache target IQN, and connect from the Win10 client the iSCSI disk.

When I tried again to create another target and using the “Query initiator computer for ID” to add the same Win10 client again, it failed with the same result.

Note: this is a clean lab setup with latest patch applied.

Is there extra step I need to take for windows 10 client compared to Windows 2016 server? Can't be the windows 10 "-" in the hostname causing the issue right??

Thanks!

Continue reading...