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

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

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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

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 notesImportant 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.

    Version

    Product

    SR_Level

    Service branch

    6.0.600 2.23xxx

    Windows Server 2008

    SP2

    LDR

    6.1.760 0.16xxx

    Windows Server 2008 R2

    RTM

    GDR

    6.1.760 0.21xxx

    Windows Server 2008 R2

    RTM

    LDR

    6.1.760 1.17xxx

    Windows Server 2008 R2

    SP1

    GDR

    6.1.760 1.22xxx

    Windows Server 2008 R2

    SP1

    LDR

  • 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 name

File version

File size

Date

Time

Platform

Isns.mof

Not applicable

10,687

16-Dec-2012

08:33

Not applicable

Isnscli.exe

6.0.6002.23004

25,600

16-Dec-2012

10:50

x86

Isnsdll.dll

6.0.6002.23004

52,224

16-Dec-2012

12:04

x86

Isnssrv.dll

6.0.6002.23004

70,144

16-Dec-2012

12:04

x86

Isnsui.exe

6.0.6002.23004

39,936

16-Dec-2012

10:50

x86

Isnsuid.dll

6.0.6002.23004

63,488

16-Dec-2012

12:04

x86

Isnswmi.dll

6.0.6002.23004

36,352

16-Dec-2012

12:04

x86

For all supported x64-based versions of Windows Server 2008

File name

File version

File size

Date

Time

Platform

Isns.mof

Not applicable

10,687

16-Dec-2012

08:32

Not applicable

Isnscli.exe

6.0.6002.23004

29,696

16-Dec-2012

11:33

x64

Isnsdll.dll

6.0.6002.23004

58,880

16-Dec-2012

12:52

x64

Isnssrv.dll

6.0.6002.23004

94,720

16-Dec-2012

12:52

x64

Isnsui.exe

6.0.6002.23004

40,448

16-Dec-2012

11:33

x64

Isnsuid.dll

6.0.6002.23004

66,048

16-Dec-2012

12:52

x64

Isnswmi.dll

6.0.6002.23004

48,640

16-Dec-2012

12:52

x64

For all supported x64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Isns.mof

Not applicable

21,438

13-Jul-2009

20:39

Not applicable

Isnscli.exe

6.1.7600.21391

26,624

06-Dec-2012

03:52

x64

Isnsdll.dll

6.1.7600.16385

58,880

14-Jul-2009

01:41

x64

Isnssrv.dll

6.1.7600.16385

95,232

14-Jul-2009

01:41

x64

Isnsui.exe

6.1.7600.16385

40,960

14-Jul-2009

01:39

x64

Isnsuid.dll

6.1.7600.16385

66,560

14-Jul-2009

01:41

x64

Isnswmi.dll

6.1.7600.16385

47,104

14-Jul-2009

01:41

x64

Isns.mof

Not applicable

21,438

20-Nov-2010

04:15

Not applicable

Isnscli.exe

6.1.7601.22182

26,624

06-Dec-2012

05:45

x64

Isnsdll.dll

6.1.7601.17514

58,880

20-Nov-2010

13:26

x64

Isnssrv.dll

6.1.7601.17514

95,232

20-Nov-2010

13:26

x64

Isnsui.exe

6.1.7601.17514

40,960

20-Nov-2010

13:24

x64

Isnsuid.dll

6.1.7601.17514

66,560

20-Nov-2010

13:26

x64

Isnswmi.dll

6.1.7601.17514

47,104

20-Nov-2010

13:26

x64


Workaround

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

Status

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

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 for Windows Server 2008 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows Server 2008

File name

X86_microsoft-windows-isns_service_31bf3856ad364e35_6.0.6002.23004_none_c413258c3fbbd42c.manifest

File version

Not applicable

File size

24,517

Date (UTC)

16-Dec-2012

Time (UTC)

12:18

Platform

Not applicable

Additional files for all supported x64-based versions of Windows Server 2008

File name

Amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.0.6002.23004_none_2031c10ff8194562.manifest

File version

Not applicable

File size

24,859

Date (UTC)

16-Dec-2012

Time (UTC)

13:10

Platform

Not applicable

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name

Amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.1.7600.21391_none_1e0ecd5d5c55df73.manifest

File version

Not applicable

File size

18,295

Date (UTC)

06-Dec-2012

Time (UTC)

14:02

Platform

Not applicable

File name

Amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.1.7601.22182_none_2000fa99597348c5.manifest

File version

Not applicable

File size

18,295

Date (UTC)

06-Dec-2012

Time (UTC)

14:01

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×