Differences

This shows you the differences between two versions of the page.

--- appnote:iscsi_targets [2013/05/07 21:00]
kes
+++ appnote:iscsi_targets [2013/05/08 07:16]
mcb30
@@ Line 4: / Line 4: @@
   * [[http://iscsitarget.sourceforge.net/|iSCSI Enterprise Target]] on Linux
   * [[http://linux-iscsi.org/|LIO (linux-iscsi.org)]] on Linux (see below)
-  * [[http://www.microsoft.com/Windowsserver2008/en/us/wss08.aspx|Windows Storage Server]] on Microsoft Windows
+  * [[http://www.microsoft.com/en-us/download/details.aspx?id=19867|Microsoft iSCSI Software Target]] (included in [[http://www.microsoft.com/Windowsserver2008/en/us/wss08.aspx|Windows Storage Server]]) on Microsoft Windows
   * [[http://hub.opensolaris.org/bin/view/Project+comstar/WebHome|COMSTAR]] on Solaris and OpenSolaris (and related products such as Nexenta and OpenIndiana)
   * [[http://www.peach.ne.jp/archives/istgt/|ISTGT]] FreeBSD iSCSI target implementation for multipath failover cluster nodes
@@ Line 15: / Line 15: @@
 === LIO (linux-iscsi.org) ===
-This target works fine, but by default sends NOP-In messages that iPXE can't handle. This should not cause any issues, but has been known to cause trouble with grub2. If you encounter this, try disabling the NOP pings by setting the ''nopin_timeout'' node attribute to 0:
+This target works fine, but by default sends NOP-In messages that iPXE can't handle.  This should not cause any issues, but has been known to cause trouble with grub2.  If you encounter this, try disabling the NOP pings by setting the ''nopin_timeout'' node attribute to zero:
     lio_node --setnodeattr <TARGET_IQN> <TPGT> <INITIATOR_IQN> nopin_timeout 0
-=== Microsoft Target Software ===
+=== Microsoft iSCSI Software Target ===
-When setting up a iSCSI target using the Initiator software it must be explicitly pointed from target to client from the server side otherwise the iSCSI target will not be available or accessible from your network. This is done by:
-iSCSITarget -> Expand iSCSI Targets -> Right click on iSCSI target -> Properties -> iSCSI Initiators tab -> Add
+You must explicitly authorise each iSCSI initiator to access each target.  Go to **Start** -> **Administrative Tools** -> **Microsoft iSCSI Software Target** and open up the list of **iSCSI Targets**.  Right-click on the relevant target and choose **Properties**.  On the **iSCSI Initiators** tab, click **Add** to authorise a new initiator.  You can specify an initiator by [[:cfg:initiator-iqn|IQN]], DNS Domain Name, [[:cfg:ip|IP Address]], or [[:cfg:mac|MAC Address]]:
+{{ :screenshots:wss_acl.png?346x295 |Adding a new initiator in Microsoft iSCSI Software Target}}
-With that screen you can authorize a client by IQN, MAC Address, IP Address or DNS Name.