Microsoft Iscsi Initiator Error

(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  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 iscsi initiator windows 2008 r2 target error local target Windows Server > File Services and Storage Question 0 Sign windows server 2008 iscsi initiator target error in to vote Running 2 Windows Server 2008 R2 Servers and Microsoft iSCSi target software on one

Iscsi Quick Connect Target Error

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

Iscsi Initiator Connection Failed

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 windows server 2012 iscsi target error 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 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

360 games PC games

Iscsi Unable To Login To The Target

Windows games Windows phone games Entertainment All Entertainment iscsi initiator quick connect failed Movies & TV Music Business & Education Business Students & educators iscsi service unavailable Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet 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 Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/2500271 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States)‎ Terms of use Privacy & cookies Trademarks © 2016 Microsoft

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 Business Learn more http://stackoverflow.com/questions/585388/iscsi-initiator-error about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each http://serverfault.com/questions/304513/error-trying-to-connect-to-iscsi-target-with-windows-initiator-on-w2k3 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 shows connection failed check firewall, when conneting using microsoft iSCSI initiator its iscsi initiator 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 Priyan R 86511124 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote microsoft iscsi initiator 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 and terms of service. Not the answer you're looking for? Browse other questions tagged iscsi or ask your own question. asked 7 years ago viewed 5345 times active 5 years ago Related -1Creating Emulated iSCSI

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 Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only 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 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 (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