Initiator Error

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow

Iscsi Initiator Windows 2008 R2 Target Error

the company Business Learn more about hiring developers or posting ads with us Stack iscsi initiator target error Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of

Iscsi Initiator Quick Connect Failed

4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up iSCSI Initiator Error up vote 0 down vote favorite When connecting to iSCSI target using starport it iscsi quick connect target error shows connection failed check firewall, when conneting using microsoft iSCSI initiator its shows target error. But there is no problem with firefall on target and initiator, AS i can connect to target port 3260 using telnet. I tried different machine and its working fine, one machine has this problem. Whats wrong this machine ? iscsi share|improve this question edited Feb 25 '09 at 9:56 kmkaplan 12.8k3553 asked Feb 25 '09 at 9:54 windows server 2012 iscsi target error Priyan R 86511124 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote What type of machine are you running the target on? What type of Target? From my experience with several iSCSI targets, MS' iSCSI Initiator is a very reliable indicator to the location of the problem. The most common reasons for getting this type of error for were - Target was listening on the wrong IP address Under Fedora, the default iptables configuration prevents incoming TCP connection of many types - including port 3260 Regarding Windows' built in rules - At least Win7 works with its built-in iSCSI initiator out-of-the-box share|improve this answer answered Feb 26 '11 at 9:33 Taichman 7961621 add a comment| up vote 0 down vote What target are you using? Turn off Windows build in rule of working with iSCSI and create manually rules, allowing access to 3260 and 3261 ports. share|improve this answer answered Sep 23 '09 at 13:50 LasseRenz add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy a

(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: iscsi initiator "target

Windows Server 2008 Iscsi Initiator Target Error

error" when connecting to local target Windows Server > File iscsi initiator connection failed Services and Storage Question 0 Sign in to vote Running 2 Windows Server 2008 R2 Servers

Iscsi Initiator Unable To Login To The Target

and Microsoft iSCSi target software on one of the servers (Server A). Setup a target and Virtual Storage on Server A. Using Microsoft iSCSi initiator http://stackoverflow.com/questions/585388/iscsi-initiator-error on both servers (Servers A and B). I can connect to target created on Server A with initiator on Server B. But I can't connect to target on Server A with the initiator on Server A. If I use the IQN for the target on Server A with the initiator on Server https://social.technet.microsoft.com/Forums/office/en-US/c2b38acc-f282-42dc-854d-c601ca489baa/iscsi-initiator-target-error-when-connecting-to-local-target?forum=winserverfiles A I get an error message that says "address cannot resolve to an ip address). If I use the IP address or FQDN for the target on Server A with the initiator on Server A I get a "target error message". The error log shows event ID 41 (WinTarget error, "The iSCSi target rejected a connection request from local computer"). Thought it might be the initiator so I downloaded the Starwind initiator client, but getting connection requests denied as well. All firewall settings and port 3260 seem fine. Any ideas on what's stopping the iscsi initator on server A from connecting to the target on Server A? Sunday, June 03, 2012 12:45 AM Reply | Quote Answers 0 Sign in to vote Running 2 Windows Server 2008 R2 Servers and Microsoft iSCSi target software on one of the servers (Server A). Setup a target and Virtual Storage on Server A. Using Microsoft iSCSi i

failover clusters Post navigation ← Previous Next → FIX: iSCSI Initiators Cannot Connect To iSCSI Target Anymore After Upgrading Windows Server 2012 iSCSI Target To Windows Server 2012 R2 Preview Posted on July 3, 2013 by workinghardinit https://blog.workinghardinit.work/2013/07/03/upgrading-windows-server-2012-iscsi-target-to-windows-server-2012-r2-preview/ I recently did an in place upgrade of my Windows Server 2012 iSCSI Target host in my home lab to Windows Server 2012 R2 Preview. That went well for one “minor” issue. My iSCSI initiators could not connect to it anymore and where in perpetual “connecting mode”. On the target the status remained in “Not Connected” for all the VHDs. As you can imagine this sort of ruins iscsi initiator the share storage experience on my test Hyper-V cluster. After checking the basics and the event logs I found nothing wrong with the iSCSI Target. It’s then that I turned to the firewall as I suspected that we could have an issue there. Sure enough, the inbound iSCSI rules on the target had not been enabled. After taking care of that the iSCSI connections succeeded and live was iscsi initiator target good again in the home lab. You only need to enable the iSCSI target rules. Like this:Like Loading... Related This entry was posted in Infrastructure, IT Pro, Upgrade and tagged Firewall, In place upgrade, iSCSI Tarhet, Windows Server 2012 R2 Preview by workinghardinit. Bookmark the permalink. 2 thoughts on “FIX: iSCSI Initiators Cannot Connect To iSCSI Target Anymore After Upgrading Windows Server 2012 iSCSI Target To Windows Server 2012 R2 Preview” Julian on August 19, 2015 at 10:38 pm said: +1, this was fantastic. Fixed my problem. Thanks very much. Reply ↓ workinghardinit on August 19, 2015 at 11:41 pm said: Always nice to hear it helped someone out! Thx for reading. Reply ↓ Leave a Reply Cancel reply Recent Posts Activating Windows Server 2016 October 14, 2016 Conferences, Presenting & Learning Q4 2016 October 6, 2016 Four MVPs have a chat after MS Ignite 2016 October 4, 2016 Recent CommentsTim on Activating Windows Server 2016workinghardinit on About WorkingHardInITworkinghardinit on SOFS / SMB 3 Offers Best VM Resiliency ExperienceHot Topics10Gbps Backups Cluster Clustering Community Compellent Conference CSV DCB DELL E2EVC Education ETS Hyper-V Kemp KMS Learning Live Migration Loadmaster Microsoft Multichannel MVP Networking NIC Teaming ODX PFC PowerShell Private Cloud RDMA R