Iscsi Initiator Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) 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 error" when connecting to local target Windows Server > File Services and Storage Question 0 iscsi initiator windows 2008 r2 target error Sign in to vote Running 2 Windows Server 2008 R2 Servers and Microsoft iscsi initiator quick connect failed iSCSi target software on one of the servers (Server A). Setup a target and Virtual Storage on Server A. Using iscsi quick connect target error Microsoft iSCSi initiator 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
Windows Server 2012 Iscsi Target Error
with the initiator on Server A. If I use the IQN for the target on Server A with the initiator on Server 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 iscsi initiator connection failed 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 initiator 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 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 g
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 I recently did an in place upgrade of windows server 2008 iscsi initiator target error my Windows Server 2012 iSCSI Target host in my home lab to Windows Server 2012
Iscsi Unable To Login To The Target
R2 Preview. That went well for one “minor” issue. My iSCSI initiators could not connect to it anymore and where in perpetual
Iscsi Initiator Failed To Connect To The Target
“connecting mode”. On the target the status remained in “Not Connected” for all the VHDs. As you can imagine this sort of ruins the share storage experience on my test Hyper-V cluster. After checking the basics and the 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 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 good again in the home lab. You only need to enable the iSCSI target rules. Like this:Like Loading... Related This entry was posted https://blog.workinghardinit.work/2013/07/03/upgrading-windows-server-2012-iscsi-target-to-windows-server-2012-r2-preview/ 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 RoCE SAN SMB 3.0 SMB Direct Storage Storage Spaces UNMAP VDI VHDX Virtualization vNext Windows 8 Windows 2008 R2 Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 Archives Archives Select Month October 2016 (4) September 2016 (2) August 2016 (4) July 2016 (5) June 20
and File SystemsPrevious: Setting Up Solaris iSCSI Targets and Initiators (Task Map)Next: Chapter 15 The format Utility (Reference)Troubleshooting iSCSI Configuration Problems The following tools are available to troubleshoot http://docs.oracle.com/cd/E19253-01/817-5093/fpjwy/index.html general iSCSI configuration problems: snoop – This tool has been updated to support iSCSI packets. wireshark – This product is available from http://www.wireshark.org/. Both tools can filter iSCSI packets on port 3260. The following sections describe various iSCSI troubleshooting and error message resolution scenarios. No Connections to the iSCSI Target From the Local System How iscsi initiator to Troubleshoot iSCSI Connection Problems Become superuser. List your iSCSI target information. For example: initiator# iscsiadm list target Target: iqn.2001-05.com.abcstorage:6-8a0900-37ad70401-bcfff02df8a421df-zzr1200-01 TPGT: default ISID: 4000002a0000 Connections: 0 If no connections are listed in the iscsiadm list target output, check the /var/adm/messages file for possible reasons why the connection failed. You can also verify whether the connection to the target is accessible by using the ping command or by connecting to the storage device's iSCSI port by using the telnet command to ensure that the iSCSI service is available. The default port is 3260. In addition, check the storage device's log file for errors. If your target is not listed in the iscsiadm list target output, check the /var/adm/messages file for possible causes. If you are using SendTargets as the discovery method, try listing the discovery-address using the -v option to ensure that the expected targets are visible to the host. For example: initiator# iscsiadm list discovery-address -v 10.0.0.1 Discovery Address: 10.0.0.1:3260 Target name: eui.210000203787dfc0 Target address: 10.0.0.1:11824 Target name: eui.210000203787e07b Target address: 10.0.0.1:11824 If you are using iSNS as the discovery method, try enabling the iSNS discovery method and listing the isns-server using the -v option to ensure that the expected targets are visible to the host. For example: initiator# iscsiadm list isns-server -v iSNS Server IP Address: 10.20.56.56:3205 Target name: iqn.