Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Unable to obtain IPv6 addresses

Unable to obtain IPv6 addresses

Overview

This article provides information and steps to resolve the issue when IPV6 addresses are not obtained. 

Only IPv4 addresses are when the Link Local IPv6 addressing is enabled for NPM installations on Windows Server 2003, Windows Server 2008 and Windows Server 2008 R2.

Environment

NPM versions 10.2 and later

Resolution

Use static DNS resolution via the hosts file. The default location of the host file is  C:\Windows\System32\Drivers\etc\

Last modified

Tags

Classifications

Public