Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Isnscli.exe incorrectly displays IPv6 address information that is from a Windows Server 2008 and Windows Server 2008 R2-based iSNS server


View products that this article applies to.

Symptoms

Assume that you use the Isnscli.exe command to retrieve information from an Internet Storage Name Service (iSNS) Server that is running Windows Server 2008 or Windows Server 2008 R2. In this situation, the Isnscli.exe command incorrectly displays IPv4 addresses instead of IPv6 addresses.

For example, you run following command: 

C:\>isnscli ListAllNodesWithDetails

The IPv6 address is incorrectly displayed as "0.0.0.93" when the Isnscli.exe command displays the following information about nodes: 

Nodes:

MSiSNSControlNode:0000031c
---
Entity Identifier: [isns:00000001]
Entity Registration Period: 900
---
iSCSI Name: [MSiSNSControlNode:0000031c]
iSCSI node type: Control
iqn.1992-08.com.netapp:sn.84d588c6e7b211e1a6bd123478563412:vs.5
---
Entity Identifier: [isns:00000002]
Entity Registration Period: 300
---
Portal IP address: 0.0.0.93
PG Portal port: 3260

↑ Back to the top


Resolution

Hotfix information

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 and Windows Server 2008 R2 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600 2.23xxxWindows Server 2008SP2LDR
    6.1.760 0.16xxxWindows Server 2008 R2RTMGDR
    6.1.760 0.21xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.17xxxWindows Server 2008 R2SP1GDR
    6.1.760 1.22xxxWindows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Server 2008 R2" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Isns.mofNot applicable10,68716-Dec-201208:33Not applicable
Isnscli.exe6.0.6002.2300425,60016-Dec-201210:50x86
Isnsdll.dll6.0.6002.2300452,22416-Dec-201212:04x86
Isnssrv.dll6.0.6002.2300470,14416-Dec-201212:04x86
Isnsui.exe6.0.6002.2300439,93616-Dec-201210:50x86
Isnsuid.dll6.0.6002.2300463,48816-Dec-201212:04x86
Isnswmi.dll6.0.6002.2300436,35216-Dec-201212:04x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Isns.mofNot applicable10,68716-Dec-201208:32Not applicable
Isnscli.exe6.0.6002.2300429,69616-Dec-201211:33x64
Isnsdll.dll6.0.6002.2300458,88016-Dec-201212:52x64
Isnssrv.dll6.0.6002.2300494,72016-Dec-201212:52x64
Isnsui.exe6.0.6002.2300440,44816-Dec-201211:33x64
Isnsuid.dll6.0.6002.2300466,04816-Dec-201212:52x64
Isnswmi.dll6.0.6002.2300448,64016-Dec-201212:52x64
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Isns.mofNot applicable21,43813-Jul-200920:39Not applicable
Isnscli.exe6.1.7600.2139126,62406-Dec-201203:52x64
Isnsdll.dll6.1.7600.1638558,88014-Jul-200901:41x64
Isnssrv.dll6.1.7600.1638595,23214-Jul-200901:41x64
Isnsui.exe6.1.7600.1638540,96014-Jul-200901:39x64
Isnsuid.dll6.1.7600.1638566,56014-Jul-200901:41x64
Isnswmi.dll6.1.7600.1638547,10414-Jul-200901:41x64
Isns.mofNot applicable21,43820-Nov-201004:15Not applicable
Isnscli.exe6.1.7601.2218226,62406-Dec-201205:45x64
Isnsdll.dll6.1.7601.1751458,88020-Nov-201013:26x64
Isnssrv.dll6.1.7601.1751495,23220-Nov-201013:26x64
Isnsui.exe6.1.7601.1751440,96020-Nov-201013:24x64
Isnsuid.dll6.1.7601.1751466,56020-Nov-201013:26x64
Isnswmi.dll6.1.7601.1751447,10420-Nov-201013:26x64

↑ Back to the top


Workaround

To this issue, retrieve the IPv6 address information from the iSNS server in the iSNS GUI.

↑ Back to the top


Status

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

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_microsoft-windows-isns_service_31bf3856ad364e35_6.0.6002.23004_none_c413258c3fbbd42c.manifest
File versionNot applicable
File size24,517
Date (UTC)16-Dec-2012
Time (UTC)12:18
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_microsoft-windows-isns_service_31bf3856ad364e35_6.0.6002.23004_none_2031c10ff8194562.manifest
File versionNot applicable
File size24,859
Date (UTC)16-Dec-2012
Time (UTC)13:10
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_microsoft-windows-isns_service_31bf3856ad364e35_6.1.7600.21391_none_1e0ecd5d5c55df73.manifest
File versionNot applicable
File size18,295
Date (UTC)06-Dec-2012
Time (UTC)14:02
PlatformNot applicable
File nameAmd64_microsoft-windows-isns_service_31bf3856ad364e35_6.1.7601.22182_none_2000fa99597348c5.manifest
File versionNot applicable
File size18,295
Date (UTC)06-Dec-2012
Time (UTC)14:01
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2789430
Revision : 1
Created on : 1/7/2017
Published on : 2/13/2013
Exists online : False
Views : 185