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) > Prevent Orion from using the SQL Server Browser service

Prevent Orion from using the SQL Server Browser service

Table of contents
Created by Mariusz Handke, last modified by MindTouch on Jun 23, 2016

Views: 918 Votes: 1 Revisions: 8

Overview

This article describes how to prevent Orion from using the SQL Server Browser service, which has been introduced in SQL Server 2005. The service listens on UDP port 1434 and is used to identify the ports where named instances of SQL Server are listening on. 

Environment

  • All Orion Core versions
  • SQL Server 2005 and later

Steps

  1. From your DBA, obtain details of the port on which SQL Server named instance listens in the following format:
    SERVER\INSTANCE_NAME,PORT
  2. Log in to the Orion server.
  3. Run the Orion Configuration Wizard.
  4. On the first screen select Database and click Next.
    Orion Configuration Wizard Database Option Selected
     
  5. Enter details from Step 1 into SQL Server field.
    Orion Configuration Wizard SQL Server Named Instance with Port
     
  6. Complete the wizard.

 

Note: If installation contains multiple Orion Servers, repeat the steps for each server.

 

Last modified

Tags

Classifications

Public