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.
Thank you for the links though. I'm going to give them a look, and if they prove to be a better solution, I'll give them a try.