iscsi initiater issue
i have given the 192.168.1.2 ip address to my ethernet and 192.168.1.14 to mu external virtual switch i am trying to find the issi target using the ethernet ip but i am not able to find it can any one provide the solution y connection is failed.
November 30th, 2013 4:41am

i have given the 192.168.1.2 ip address to my ethernet and 192.168.1.14 to mu external virtual switch i am trying to find the issi target using the ethernet ip but i am not able to find it can any one provide the solution y connection is failed.
You need to "ping" port 3260 as it's where MS target listens by default. Did you open the iSCSI port in firewall BTW?
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2013 12:52pm

i disable all firewall from the system........and one think more i am using normal hard disk so is there nay need to have seperate  iscsi storage or it will work with normal hard disk..
November 30th, 2013 3:23pm

also one thing more i created iscsi target using istorage still no success and try to find using the 192.168.1.2
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2013 4:41pm

also one thing more i created iscsi target using istorage still no success and try to find using the 192.168.1.2
  • Edited by asif tahir Saturday, November 30, 2013 9:06 PM
December 1st, 2013 12:06am

also one thing more i created iscsi target using istorage still no success and try to find using the 192.168.1.2

NEC iStorage is a very rare beast in Hyper-V infrastructure. So the best way to get help is to ask from vendor directly. My $0.02... See:

http://jpn.nec.com/istorage/

Good luck!

Free Windows Admin Tool Kit Click here and download it now
December 1st, 2013 5:38am

i dont have any iscsi storage i am using normail hardisk tht the problem i am facing
December 1st, 2013 3:20pm

and do u have any idea about configuring the storage on private cloud.........
Free Windows Admin Tool Kit Click here and download it now
December 1st, 2013 3:21pm

Hi,

If you cannot find the Target name, please try to assign the Target with IQN:*, which means any initiator can access this Target. It is not a recommended practice, but a good troubleshooting technique.

For more detailed information, please refer to the article below:

Introduction of iSCSI Target in Windows Server 2012
http://blogs.technet.com/b/filecab/archive/2012/05/21/introduction-of-iscsi-target-in-windows-server-2012.aspx

Regards,
December 2nd, 2013 3:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics