"Unable to connect to the computer" error when you try to manage iSCSI virtual disks in Windows Server 2012

Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 Essentials


Consider the following scenario:
  • You have a Windows domain, for which the DNS label contains only a single character.
  • You install the iSCSI Target role service on a domain member that runs Windows Server 2012.
  • You try to create an iSCSI virtual disk that uses either the iSCSI PowerShell cmdlet or the "New iSCSI Virtual Disk" wizard.
In this scenario, you receive the following error message:
Unable to connect to the computer.
The iSCSI Target role service runs a verification of the server DNS name before it connects. This verification fails for domains that contain a single character DNS label.

How to obtain the hotfix

To resolve this issue, we have released a hotfix for Windows Server 2012 and Windows 8.

Note To resolve this issue in Windows Server 2012 R2, you can apply hotfix KB2953557.

Hotfix information for Windows Server 2012 and Windows 8

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


There is no prerequisite to apply this hotfix.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

More Information


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


See the terminology that Microsoft uses to describe software updates.