Dell PowerVault NX3100 - Manual (Page 53)

Appendix
53
server running Microsoft iSCSI Software Target has IP addresses that are
not used to communicate with the Initiator. The Initiator attempts to
connect to each configured IP address and waits up to 100 seconds for a
response. This issue can also be caused by automatic private IP address
assignments (169.x.x.x). To prevent this issue, use static IP addresses
where DHCP is unavailable.
The following options provide a workaround for this issue:
– Specify the source and target portal by IP address.
– Use only IPv4 addresses or IPv6 addresses: do not mix the types of
address.
– Disable network cards that are not connected to a network.
• Errors in Event Viewer—You may encounter errors in the Event Viewer
when you attempt to uninstall Microsoft iSCSI Software Target 3.2 and
reinstall it again. As a workaround, stop the Microsoft iSCSI Software
Target service before uninstalling the software. If the software has already
been uninstalled, restart the computer before reinstalling Microsoft iSCSI
Software Target.
• Additional Firewall rules for iSCSI Initiators—You may need to enable
additional rules to connect an iSCSI Initiator to Microsoft iSCSI Software
Target on Windows Storage Server 2008. The following Windows Firewall
rules are required:
– Windows Management Instrumentation (WMI-In) [TCP/All ports]
– Windows Management Instrumentation (DCOM-In) [TCP/Port 135]
– Windows Management Instrumentation (ASync-In) [TCP/All ports]
– Windows Management Instrumentation (WMI-Out) [TCP/All ports]
– Remote Volume Management (RPC-EPMAP) [TCP/RPC Endpoint
Mapper]
– Remote Volume Management - Virtual Disk Service Loader (RPC)
[TCP/Dynamic RPC]
– Remote Volume Management - Virtual Disk Service (RPC)
[TCP/Dynamic RPC]