Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Binding the Orion Web Console to a host name

Binding the Orion Web Console to a host name

Table of contents

Updated March 14, 2017

Overview

If you added a site binding to a host name before you upgrade, you must bind the Orion Web Console to a fully qualified domain name (FQDN).

 

If you upgrade any SolarWinds Orion product without binding to a FQDN, the top menu may disappear. In this case, bind the Orion Web Console to an FQDN and restart IIS.

 

Environment

Products running on Orion Platform 2017.1, such as:

  • NPM 12.1
  • SAM 6.4
  • NTA 4.2.2
  • NCM 7.6
  • SRM 6.4
  • Integrated VMAN 7.1
  • VNQM 4.4

Detail

If you setup IIS to use host name bindings for the Orion Web Console, you must use the fully qualified domain name.

  1. Log in to the Orion server as an administrator.
  2. Open IIS Manager.
  3. Expand Sites and select your SolarWinds website.
  4. Click 'Bindings' under Actions.
  5. Change the host name to a FQDN.
  6. Restart IIS.
 

 

Last modified

Tags

Classifications

Public