network ports used by SQL Monitor

SQL Server performance monitoring and alerting

Moderators: Colin Millerchip, priyasinha, Adam, chriskelly

network ports used by SQL Monitor

Postby TheLonelyDBA » Tue Mar 11, 2014 9:49 pm

So I am testing SQL Monitor Hosted, but I assume the on-premise installation would face the same issue.

I need to monitor several SQL Servers that are on firewalled networks. Some are on the same domain, some are on distinct domains and will use local windows accounts to be monitored.

My issue is that I have not found the list of ports that I need to open on the firewall, in order to make the Relay Service be able do see the monitored server.

I already opened SQL standard port 1433, but when I add the server in the Configuration page it says:

Status: Unreachable (Cannot connect)

the error details are:

Date: 11 Mar 2014 5:44 PM
Group: Registry
Event: OpenRegistryHive: LocalMachine
Outcome: Cannot connect
Exception: Win32Exception
Exception message: The network path was not found

Can someone post a list of ports that I need to open on my firewall to get monitoring working?

thanks,
Tips and thoughts on MS SQL, Oracle and MongoDB:
http://thelonelydba.wordpress.com
TheLonelyDBA
 
Posts: 18
Joined: Wed Oct 30, 2013 8:01 pm
Location: Brazil

Postby TheLonelyDBA » Thu Mar 13, 2014 7:14 pm

UP!

no word on port numbers? does anyone have experience with such restricted/firewalled environments?

regards
Tips and thoughts on MS SQL, Oracle and MongoDB:
http://thelonelydba.wordpress.com
TheLonelyDBA
 
Posts: 18
Joined: Wed Oct 30, 2013 8:01 pm
Location: Brazil

Postby fionag » Tue Mar 18, 2014 6:30 pm

The following page outlines the ports you need to open for the on-premise version of SQL Monitor
http://documentation.red-gate.com/pages ... d=17270675
Whilst not specific to hosted, the same principle should apply.

Additionally the hosted relay uses port 23547 to communicate with Red Gate’s servers.
fionag
 
Posts: 34
Joined: Thu Jan 05, 2012 5:40 pm
Location: Red Gate

Postby TheLonelyDBA » Thu Apr 10, 2014 3:04 pm

hi Fiona. I got the relay to talk with the web server of the SQL Monitor Hosted service.

Also my firewall team was able to open a bunch of ports on the internal network, but we could not get the server to use a fixed port for wmi.

Is it possible to monitor only SQL events and ignore all data captured via WMI in some way?

PS: ports opened both ways:
TCP 139
TCP 445
TCP 135
TCP 137
TCP 24158
UDP 137
Tips and thoughts on MS SQL, Oracle and MongoDB:
http://thelonelydba.wordpress.com
TheLonelyDBA
 
Posts: 18
Joined: Wed Oct 30, 2013 8:01 pm
Location: Brazil

Postby fionag » Tue Apr 15, 2014 11:33 am

It doesn't help to disable the WMI part of the monitoring because the underlying problem is with DCOM on which WMI and remote registry are built. Whilst you could disable WMI, disabling remote registry would remove much of the product’s usefulness.

In order for monitoring to succeed, the following network traffic needs to be opened up (see http://support.microsoft.com/kb/832017/en-gb):
ICMP Ping
Port 135
Port 445
Ports 49152-65535 (for Windows Server 2008 or later)
Ports 1023-5000 (for Windows Server 2003 or earlier)

These are all covered by the following Windows Firewall rules/exceptions:
All ICMP v4
Core Networking
File and Printer Sharing
SQL Server
Windows Management Instrumentation (WMI)

I hope that is of some help.
Fiona
fionag
 
Posts: 34
Joined: Thu Jan 05, 2012 5:40 pm
Location: Red Gate


Return to SQL Monitor 4

Who is online

Users browsing this forum: No registered users and 0 guests