Date: Thu, 28 Mar 2024 10:08:47 +0000 (GMT)
Message-ID: <1620095094.381.1711620527154@ip-172-31-38-4.eu-west-1.compute.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_380_252706922.1711620527148"
------=_Part_380_252706922.1711620527148
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
If you are unable to view the SQL Monitor w=
eb page, and your browser displays a "cannot connect" type message, then yo=
u may need to check that SQL Monitor is not being blocked by the firewall o=
n the web server machine.
If possible, install the Base Monitor on a server t=
hat does not need to go through a firewall to access the SQL Servers you wa=
nt to monitor. If your network configuration prevents this, then we recomme=
nd that you use a VPN link between the Base Monitor and the monitored SQL S=
ervers.
To allow access to SQL Monitor through the firewall=
, follow the steps below.
Allow access to TCP ports and WMI
SQL Monitor requires access to:
- TCP port 135 used by the Remote Procedure Call (=
RPC) service. Also make sure that the remote registry service is started on=
the server.
- TCP port 445 used by the Server Message Block (S=
MB) service that allows remote file access.
- TCP port 1433 used as the default registered add=
ress for the SQL Server Database Engine. If your SQL Server uses a differen=
t TCP configuration, use that port number instead.
- WMI. You will need to configure each server you =
want to monitor separately. See the following:
<=
a class=3D"external-link" href=3D"http://msdn.microsoft.com/en-us/library/a=
a389286%28v=3Dvs.85%29.aspx" title=3D"Connecting Through Windows Firewall" =
rel=3D"nofollow">Connecting Through Windows Firewall
Setting Namespace Security with the WMI C=
ontrol
Security a Remote WMI Connectio=
n
Setting Up a Fixed Port for =
WMI
For XP, Vista and Windows Server 2003 a=
nd 2008
- Open the Control Panel<=
/strong> on the machine where you installed the SQL Monitor Web Server.
- Go to Security Center <=
/strong>and click Windows Firewall.
- Click Change settings=
strong>.
- Under Exceptions, click Add port and then enter a name and the port number.You can use an=
y name to identify that this exception is for SQL Monitor.
The port number should be your SQL Monitor web server port number, specifi=
ed during installation; this is 8080 by default.
- Click OK.
For Windows 7
- On the machine where you installed the SQL Monit=
or Web Server, open Windows Firewall with Advanced=
Security:=20
- Type "Firewall" into the Search programs and fi=
les box, or
- From the Control Panel, select System and Security then Windows=
Firewall then Advanced settings=
.
- Click Inbound Rules.
- Click New Rule=
.
- Select Port as=
the type of rule you want to create, then click N=
ext.
- Choose TCP as =
the port type, then under Specific local ports, enter the SQL Monitor port number.
Your SQL Monitor web server port number is specified during installation; =
this is 8080 by default.
- Click Next, th=
en select Allow the connection.
- Click Next, th=
en choose the type of profile to apply the rule to.
- Click Next, th=
en enter a name to identify that this exception to your firewall is for SQL=
Monitor.
- Click Finish.<=
/li>
Further information
For XP, see the following Microsoft KB article: http://support.microsoft.com/kb/842242
For Windows 7, see the following Microsoft article:=
http://windows.microsoft.com/en-us/windows7/Allow-a-program-=
to-communicate-through-Windows-Firewall
------=_Part_380_252706922.1711620527148--