Solved

Connection failed with iSCSI on Hyper-V Server

Posted on 2014-10-28
4
441 Views
Last Modified: 2014-11-02
I have a Windows 2012 Storage Server with multiple iSCSI targets defined.  I have three other servers, each connecting to one target.  One of the server is a Hyper V 2012 R2 Core Server.

The Hyper-V Server has its VMs on the iSCSI Drive.  The problem is, I reinstalled the Hyper V operating system today due to a disk failure, and the new installation is unable to connect to the iSCSI Drive.  Each time I try to Discover the iSCSI Targets I receive a Connection Failed error.  I receive the same when I try to enter the SNS server address.

There is obviously no problem with the Storage server as it worked before, and still works for the other two servers.  So I expect the problem to be on the Hyper-V server.  

I have set the iSCSI service to Automatic, and confirmed it is running.  I have enabled iSCSI in the Windows Firewall.  

I can ping in both directions, using DNS name and IP address, so the network addressing is okay.  I do not remember having to do anything other than that the first time I set it up to get iSCSI running.

I have confirmed the settings of the target to confirm the initiator settings are correct based on iqn and IP address.

I have also, just on the off chance, restarted both server.

So now I am at a loss.  I am hoping someone can tell me what step or setting I have missed.
0
Comment
Question by:townsma
  • 3
4 Comments
 
LVL 42

Expert Comment

by:kevinhsieh
ID: 40409904
Try to change the ACL on the volume so that either any initiator can connect, or limit to just the iSCSI initiator name. It's possible that you are requiring chap authentication or that the Hyper-V host is trying to connect from another IP that isn't allowed.
0
 
LVL 6

Author Comment

by:townsma
ID: 40409907
I presume you mean on the target, not the volume?

I tried to limit it by the iqn only, No difference.

As we use this on a private development LAN we do not use any form of chap authentication.
0
 
LVL 6

Accepted Solution

by:
townsma earned 0 total points
ID: 40409928
I have resolved the problem.  

The iSNS ports were not opened on the Hyper-V server.  It is not mentioned in any of my internet searches.  I found is in the iSCSI User Guide for WIn Server 2008 Core.

Also, I changed the iSCSI target ACL for just the IP address, not using the iqn.

Now it works and is connected correctly.
0
 
LVL 6

Author Closing Comment

by:townsma
ID: 40417997
I have provided the solution.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is an issue that we can get adding / removing permissions in the vCSA 6.0. We can also have issues searching for users / groups in the AD (using your identify sources). This is how one of the ways to handle this issues and fix it.
Is your company's data protection keeping pace with virtualization? Here are 7 dynamic ways to adapt to rapid breakthroughs in technology.
This video teaches viewers how to encrypt an external drive that requires a password to read and edit the drive. All tasks are done in Disk Utility. Plug in the external drive you wish to encrypt: Make sure all previous data on the drive has been …
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now