Iscsi Initiator Windows 2003 Target Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums 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 iscsi connection failed Server > File Services and Storage Question 0 Sign in to vote Running 2
Iscsi Initiator Windows 2008 R2 Target Error
Windows Server 2008 R2 Servers and Microsoft iSCSi target software on one of the servers (Server A). Setup a target iscsi initiator quick connect failed 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 iscsi add target portal connection failed 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 get a "target
Iscsi Initiator Failed To Connect To The 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 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 Se
Start 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 the company iscsi virtual disk status not connected Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags iscsi initiator unable to login to the target Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only
Windows Server 2012 Iscsi Initiator Reconnecting
takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Error trying to connect to iscsi target with Windows https://social.technet.microsoft.com/Forums/windowsserver/en-US/c2b38acc-f282-42dc-854d-c601ca489baa/iscsi-initiator-target-error-when-connecting-to-local-target?forum=winserverfiles initiator on W2K3 up vote 1 down vote favorite I am trying to connect to an iScsi array (hosted on a QNAP 859URP+) from my W2K3, via a 2nd NIC. I have my QNAP 859URP+ connected through LAN1 to my switch. It gets it's IP from our DHCP server. I want to connect LAN2 directly to the server. I have the following settings: QNAP LAN1 (connected to switch) IP: 192.168.0.9 MASK: 255.255.255.0 Gateway: 192.168.0.254 QNAP LAN2 http://serverfault.com/questions/304513/error-trying-to-connect-to-iscsi-target-with-windows-initiator-on-w2k3 (connected to the 2nd NIC on the server) IP: 192.168.111.1 (default) MASK: 255.255.255.0 Gateway: NONE On the server, the 2NIC that is connected to the QNAP LAN2 has the following: IP: 192.168.111.2 MASK: 255.255.255.0 GATEWAY: NONE (first NIC is DHCP'ed) I am able to ping to the 192.168.111.1 from the server (and not from any other pc/server on the network - that's good), but when trying to access/add from the Windows iScsi Initiator - I get an error: connection failed. Port is the default 3260 no firewalls are installed What am I doing wrong? windows-server-2003 iscsi qnap share|improve this question edited Aug 24 '11 at 13:47 asked Aug 24 '11 at 13:34 Saariko 87073165 I have found the problem to be a security setting on the QNAP. I have limited access to the QNAP from IP range of: 192.168.0.1-254. Changing that solved the problem –Saariko Aug 24 '11 at 14:56 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted I have found the problem to be a security setting on the QNAP. I have limited access to the QNAP from IP range of: 192.168.0.1-254. Changing that solved the problem share|improve this answer answered Sep 12 '11 at 11:55 Saariko 87073165 add a comment| Your Answer draft saved draft discarded Sign up or log in S
WindowsWindows 10 Windows Server 2012 Windows Server 2008 Windows Server 2003 Windows 8 Windows 7 Windows Vista Windows XP Exchange ServerExchange Server 2013 Exchange Server 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync SharePoint Virtualization Cloud Systems http://windowsitpro.com/storage/q-im-using-microsoft-iscsi-target-thats-available-windows-storage-server-2008-when-i-try-con ManagementSystem Center PowerShell & Scripting Active Directory & Group Policy Mobile Networking Storage TrainingOnline Training IT/Dev Connections Webcasts VIP Library Digital Magazine Archives InfoCentersIT Innovators Mobile Computing Business Now Desktop VDI All About Converged Architecture Advertisement Home https://community.spiceworks.com/topic/170976-how-do-i-troubleshoot-iscsi-error-connection-to-the-target-was-lost > Systems Management > Storage > Q. I'm using the Microsoft iSCSI Target that's available for Windows Storage Server 2008, but when I try to connect to the target to perform discovery I see no targets. What's iscsi initiator wrong? Q. I'm using the Microsoft iSCSI Target that's available for Windows Storage Server 2008, but when I try to connect to the target to perform discovery I see no targets. What's wrong? Jan 17, 2010 John Savill | Windows IT Pro EMAIL Tweet Comments 0 Advertisement A. Assuming you've configured iSCSI correctly, have enabled all the necessary firewall exceptions, and have IP connectivity, the next item would be to connect to the iscsi initiator windows iSCSI target. The easiest way is using the Discover Portal under the Discovery tab of the iSCSI Initiator administrative tool. Just type in the IP address or name of the iSCSI target, as shown. You should see a list of available targets under the Targets tab after clicking Refresh, but you may not see any. The most likely cause for not seeing the targets is that you haven't added the initiator's iSCSI Qualified Name (IQN) to the target. The only targets shown are those that the initiator has permission to use, so if you haven't added the initiator IQN to the allowed list for the target, no targets will be displayed. To resolve this, add the initiator's IQN to the allowed list: Access the Microsoft iSCSI Software Target management interface (Server Manager, Storage, Microsoft iSCSI Software Target). Expand iSCSI Targets. Right-click a target that the client should be able to access and select Properties. Select the iSCSI Initiators tab. Click the Add button and enter the IQN of the initiator (you can check the IQN of the initiator through the Configuration tab of the iSCSI Initiator app on the client). Click to expand. Click OK to all dialogs. On the iSCSI Initiator Targets tab, click Refresh and the targets to which the initiator has access will be displayed. Relat
Community! Creating your account only takes a few minutes. Join Now My biggest problem is the Event Id 20 from source ISCSIPRT which reads "connection to the target was lost. the initiator will attempt to retry the connection". I want to monitor this and try to see the symptoms before it actually happens. Background on my environment: - Dedicated Netgear GS716T gigabit switch just for SAN traffic on its own 10.0.0.x subnet. Flow control is on. Jumbo Frames is off. Spanning tree is off. Using CAT 6 network cables - Infortrend Eonstor SAN device with 2 ethernet ports. 12 TB raw disk using RAID 6 giving a little less than 8 TB usable. I have set it up as 1 Logical Drive with 7 several partitions. Partitions 1,2,3 each have their own LUN and are going thru NIC #1. Partitions 4,5,6,7 have each have their own LUN and are going thru NIC #2. Jumbo frames is off. NOT using any Multipathing feature as the vendor is not supporting LUN MASKING (A BIG DRAWBACK FOR ME!!!!) - Server #1 is running Windows 2003 Std SP2 32-bit using Ms iscsi initiator to connect to iscsi target on NIC #1. That gives 3 drives appearing on the server (partitions 1,2,3). Server #1 is using dedicated NIC for SAN traffic which is Intel Pro 1000 MT Server NIC. I then have several folders shared out on network for clients to access. - Server #2 is running Windows 2003 Small Business Server Standard SP2 32-bit using MS iscsi initiator connecting to target on NIC #2. that gives 4 drives appearing on the server (partitions 4,5,6,7). Server #2 is using dedicated NIC for SAN traffic which is Intel Pro 1000 MT Server NIC. I then have several folders shared out on network for clients to access. Here are some of the steps I've taken: ... I've added a few counters to the Windows performance monitor. I found this post thru the MS Technet Performance Team blog which offers a few ideas: http://blogs.technet.com/b/askperf/archive/2010/12/03/performance-counter-for-iscsi.aspx
... Also, according to MS Iscsi initiator guidelines, I have modified registry to change the TcpAckFrequency to a value of 1 ( HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces ) ... I have made sure that the TCP Nagle algoritm is turned off according to the following suggestion: http://smallvoid.com/article/winnt-nagle-algorithm.html Anyone else find ways to pay attention to your iSCSI connections? EDIT: I also followed the instructions in this MS KB article "In Windows Server 2008 or Windows Server 2008 R2 environment, if the network environment is set to enable Delay ACK and storage is connec