iSCSI connection-Server 2008 R2 to Dell MD3000i

We've got a Dell MD3000i with 2 datastores configured.  One server connects to each datastore.  I recently re-installed the OS on one of the servers (went from Server Core to Server 2008 R2) and am unable to get the connection working again between this server and the SAN.

I added the server's iSCSI intitiator name to the SAN, I have 2 NICs in the server both configured on the same subnet as the SAN controllers.  When I try to discover any of the controller IP addresses in Windows iSCSI intitiator, I get a dialog saying "Connection Failed" and 3 events logged in Event Viewer.
screenshot
I've mirrored the settings for the NICs from the server that is still attached and I cannot figure out why I can't connect to the MD3000i.  Any suggestions?  Thanks.
LVL 1
cciservicesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cciservicesAuthor Commented:
Also, I disabled the firewall while attempting to get the server and storage connected.
0
emadallanCommented:
0
cciservicesAuthor Commented:
I've already viewed that and it is not helpful.
Addressing each of the possible causes in that article:
Cause 1: The name and IP of the iSCSI target have not changed.
Cause 2: The target cannot have reached it's max number of incoming connections because we had two before and now we only have one.  I am trying to establish the second connection.
Cause 3: I suppose this is possible, but just saying "a transient network issue prevented connectivity" doesn't help resolve what is preventing the connection.
Cause 4: The network stack is not fully prepared.  Again I suppose this is possible, but there are no troubleshooting steps or advice on how to diagnose this.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

emadallanCommented:
try to reconfigure your iscsi setting from scratch.
0
cciservicesAuthor Commented:
Done that several times already.
0
emadallanCommented:
try thtis:

from the properties of your iscsi initiator, click on discovery tab, you will see that both ip address and card are selected by default, we need to change that to ip address of your SAN portal and you ip of inintiator, so click discover portal button, then enter the ip address of your SAN Portal with the port 3260, after that click on the advanced button and select the ip address of your initiator instead of by default.

to learn more about this issue search google of what does mean: Portal Hopping in ISCSI.
0
emadallanCommented:
if your french language is good then visit:
http://www.winmgr.com/?p=1391
good luck!
0
cciservicesAuthor Commented:
Nope.  I've tried it both ways, with portal hopping (using Default for Adapter and IP Address) and by explicitly telling it the Adapter and initiator IP to use.  Both ways result in "Connection failed"
0
cciservicesAuthor Commented:
Question: Should I be able to ping the IP address of a controller on the MD3000i BEFORE getting the iSCSI connection functioning?
0
emadallanCommented:
note someone said i Resolved this issue by manually add 3260/3261 inbound ports to Windows Firewall to access Starwind ISCSI Targets. This should be done automatically during install.
0
cciservicesAuthor Commented:
Right, but I have the firewall turned off.
0
emadallanCommented:
yes of course you should have the ping functional from your iscsi initiator to your iscsi target
0
emadallanCommented:
I would guess the problem is at the target. Try to connect using a crossover cable to see if there might be some kind of issue between the target and initiator
0
cciservicesAuthor Commented:
I did not change anything with the storage array.  All I did was re-install the OS on a server.  I didn't move any wires.  It has to be a configuration issue that I am missing or don't understand.
0
emadallanCommented:
Check the ports,  are the same on the target?
0
cciservicesAuthor Commented:
I don't understand your question.
0
cciservicesAuthor Commented:
I've got it figured out.  I was going off of a network diagram that doesn't match the physical wiring.  I noticed it when I checked the VLAN configuration on the switch between the server and the storage array.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cciservicesAuthor Commented:
In looking at the switch, I saw that the VLAN IDs did not match the network diagram I had.  I figured this out on my own, so I am accepting my own comment as the solution.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Architecture

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.