This topic lists some common issues that you may encounter when using Storage Explorer. For more troubleshooting information, see https://go.microsoft.com/fwlink/?LinkId=94678.

What problem are you having?

I am not able to see my iSCSI fabric under iSCSI Fabrics.
  • Cause:  Possible causes include:

    • Discovery of iSCSI nodes is achieved by querying Internet Storage Name Service (iSNS) servers in your storage area network (SAN). If there are no iSNS servers in your SAN, or if the iSCSI initiators and targets have not been configured to use an iSNS server for discovery, you will not be able to see your iSCSI fabric.

    • Firewall restrictions are blocking your server from communicating with other servers in your SAN.

    • Computers in your SAN are not part of a domain. Storage Explorer can only discover computers that have a fully qualified domain name (FQDN).

  • Solution:  Resolutions include:

    • If you do not have any iSNS servers in your SAN, you first need to install one. On a computer running Windows Server 2008 or later, you can install Internet Storage Name Server using Server Manager (in the Features node, click Add Features). On a computer running Windows 2000 or Windows Server 2003, you can download and install Microsoft iSNS Server 3.0 from the Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkID=94670).

      After you have installed one or more iSNS servers, configure each iSCSI initiator and target in your SAN to use an iSNS server for discovery. This configuration is done in the configuration tools for initiators and targets, such as iSCSI Initiator in Control Panel.

    • Enable the Windows Management Instrumentation (WMI) exception on every server running Windows Server 2008 or later that is part of your fabric. You can enable this exception by using Windows Firewall from Control Panel. For more information, see https://go.microsoft.com/fwlink/?LinkID=94683.

    • Make sure that all computers in your SAN are part of a domain and that they have a valid FQDN.

I am not able to see my Fibre Channel fabric under Fibre Channel Fabrics.
  • Cause:  Possible causes include:

    • Discovery of Fibre Channel nodes is partly achieved by querying the Fibre Channel switches in your SAN. The Fibre Channel commands that a switch can support depend on the hardware manufacturer of the switch, the model of the switch, and the version of the firmware running on the switch. If a switch does not support the commands issued by Storage Explorer, you will not be able to see that switch, and possibly some of the servers connected to it.

    • Firewall restrictions are blocking your server from communicating with other servers in your SAN.

    • Computers in your SAN are not part of a domain. Storage Explorer can only discover computers that have a fully qualified domain name (FQDN).

  • Solution:  Resolutions include:

    • Contact the manufacturer of your Fibre Channel switch and verify that it is compatible with Storage Explorer.

    • Enable the Windows Management Instrumentation (WMI) exception on every server running Windows Server 2008 or later that is part of your fabric. You can enable this exception by using Windows Firewall from Control Panel. For more information, see https://go.microsoft.com/fwlink/?LinkID=94683.

    • Make sure that all computers in your SAN are part of a domain and that they have a valid FQDN.

I cannot connect to a remote computer using Storage Explorer.
  • Cause:  The Windows Management Instrumentation (WMI) exception on the remote computer is not enabled, or you are not logged on using a domain account that is a member of the Administrators group on the remote computer.

  • Solution:  Use Windows Firewall in Control Panel to enable the Windows Management Instrumentation (WMI) exception on the remote computer. For more information, see https://go.microsoft.com/fwlink/?LinkID=94683.

    Also, ensure that the account you used to log on to the local computer is a member of the Administrators group on the remote computer. For more information, see Connecting to a Remote Computer.

Additional references

Table Of Contents