The following tip is excerpted from my book Training Guide: Installing and Configuring Windows Server 2012 from Microsoft Press:
http://www.wservernews.com/go/1398330331089
If your attempt to discover an iSCSI target fails, it is usually for one of the following reasons:
- The wrong target portal IP address or DNS name was configured on the initiator.
- The wrong IQN for the initiator was assigned when the target was created.
- There are problems with network connectivity between the initiator and target computers.
Troubleshooting the first issue is straightforward. To see if the second issue is the cause of the problem, try assigning IQN* as the target, which allows any initiator to connect to it. And, of course, you can troubleshoot the third issue using standard network troubleshooting procedures.
The above tip was previously published in an issue of WServerNews, a weekly newsletter from TechGenix that focuses on the administration, management and security of the Windows Server platform in particular and cloud solutions in general. Subscribe to WServerNews today by going to http://www.wservernews.com/subscribe.htm and join almost 100,000 other IT professionals around the world who read our newsletter!
Mitch Tulloch is a twelve-time recipient of the Microsoft Most Valuable Professional (MVP) award and a widely recognized expert on Windows Server and cloud computing technologies. Mitch is also Senior Editor of WServerNews. For more information about him see http://www.mtit.com.
