The other ports don't appear like typical MSSQL ports. Do you have by any chance the Windows firewall still active? Maybe the port is being blocked there? <a href="http://support.microsoft.com/kb/968872">http://support.microsoft.com/kb/968872</a> Or do you use a named instance? I found this information on <a href="http://benchmarkitconsulting.com/colin-stasiuk/2009/02/02/what-tcp-port-is-sql-server-running-under/">http://benchmarkitconsulting.com/colin-stasiuk/2009/02/02/what-tcp-port-is-sql-server-running-under/</a>: "If you have a named instance the TCP port is dynamically configured." I've never seen this in a practical way before though. <div class="gmail_quote">On Thu, Nov 17, 2011 at 8:59 PM, Kaplan, Andrew H. <<a href="mailto:AHKAPLAN@partners.org">AHKAPLAN@partners.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div> <div dir="ltr" align="left">Hi there --</div> <div dir="ltr" align="left"> </div> <div dir="ltr" align="left">I tried connecting to port 1433 of the SQL server, and the connection was refused. It appears that efforts to connect via the default</div> <div dir="ltr" align="left">port will not work in this case. I took the liberty of running the nestat -abn command syntax on the console of the SQL server, and</div> <div dir="ltr" align="left">searched for all references to the sqlservr.exe binary. The results are shown below:</div> <div dir="ltr" align="left"> </div> <div dir="ltr" align="left"> Active Connections [sqlservr.exe] TCP <a href="http://0.0.0.0:58477" target="_blank">0.0.0.0:58477</a> <a href="http://0.0.0.0:0" target="_blank">0.0.0.0:0</a> LISTENING [sqlservr.exe] TCP <a href="http://0.0.0.0:62502" target="_blank">0.0.0.0:62502</a> <a href="http://0.0.0.0:0" target="_blank">0.0.0.0:0</a> LISTENING [sqlservr.exe] TCP <a href="http://0.0.0.0:65249" target="_blank">0.0.0.0:65249</a> <a href="http://0.0.0.0:0" target="_blank">0.0.0.0:0</a> LISTENING [sqlservr.exe] TCP <a href="http://127.0.0.1:58751" target="_blank">127.0.0.1:58751</a> <a href="http://0.0.0.0:0" target="_blank">0.0.0.0:0</a> LISTENING [sqlservr.exe] TCP <a href="http://127.0.0.1:62503" target="_blank">127.0.0.1:62503</a> <a href="http://0.0.0.0:0" target="_blank">0.0.0.0:0</a> LISTENING [sqlservr.exe] TCP <a href="http://127.0.0.1:63954" target="_blank">127.0.0.1:63954</a> <a href="http://127.0.0.1:63955" target="_blank">127.0.0.1:63955</a> ESTABLISHED [sqlservr.exe] TCP <a href="http://192.168.40.114:62502" target="_blank">192.168.40.114:62502</a> <a href="http://192.168.40.122:50342" target="_blank">192.168.40.122:50342</a> ESTABLISHED [sqlservr.exe] TCP <a href="http://192.168.40.114:62502" target="_blank">192.168.40.114:62502</a> <a href="http://192.168.40.125:60257" target="_blank">192.168.40.125:60257</a> ESTABLISHED [sqlservr.exe] TCP <a href="http://192.168.125.1:139" target="_blank">192.168.125.1:139</a> <a href="http://0.0.0.0:0" target="_blank">0.0.0.0:0</a> LISTENING [sqlservr.exe] TCP [::]:58477 [::]:0 LISTENING [sqlservr.exe] TCP [::]:62502 [::]:0 LISTENING [sqlservr.exe] TCP [::]:65249 [::]:0 LISTENING [sqlservr.exe] TCP [::1]:58751 [::]:0 LISTENING [sqlservr.exe] TCP [::1]:62005 [::1]:62006 ESTABLISHED [sqlservr.exe] UDP <a href="http://0.0.0.0:123" target="_blank">0.0.0.0:123</a> *:* If the default port, 1433, is not reachable would one the above ports be the alternate means of connecting to the server? </div> <div dir="ltr" lang="en-us" align="left"> <hr> From: Claudio Kuenzler [mailto:<a href="mailto:ck@claudiokuenzler.com" target="_blank">ck@claudiokuenzler.com</a>] Sent: Thursday, November 17, 2011 1:39 PM<div class="im"> To: Nagios Users List Subject: Re: [Nagios-users] Monitoring a Microsoft SQL Server </div> </div><div><div></div><div class="h5"> <div></div>Please let us know if you get it working - I might have to add such a check soon as well. To answer your question: 1433 is the standard port of MSSQL so that should be ok. You can launch nmap or a simple telnet to double-check that. <div class="gmail_quote">On Thu, Nov 17, 2011 at 4:34 PM, Jim Avery <<a href="mailto:jim@jimavery.me.uk" target="_blank">jim@jimavery.me.uk</a>> wrote: <blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote"> <div>On 17 November 2011 15:17, Kaplan, Andrew H. <<a href="mailto:AHKAPLAN@partners.org" target="_blank">AHKAPLAN@partners.org</a>> wrote: > Hi there -- > > Thanks for your reply. I tried your suggestion on the two plugins, and here are > the results. > > When the command syntax for check_mssql was the following: > > ./check_mssql -H <ip address> -U <domain>\\<username> -P <password> > > or > > ./check_mssql -H <ip address> -U '<domain>\\<username>' -P <password> > > The error message displayed on-screen was: > > UNKNOWN: Invalid characters in the username. </div>The check_mssql plugin is way too fussy about what characters it will allow in host names and user names. On my system I edited the plugin to remove the if/else sections entirely below the comments "// Validate the hostname" and "// Validate the username". hth, Jim <div> <div></div> <div> ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. <a href="http://p.sf.net/sfu/splunk-novd2d" target="_blank">http://p.sf.net/sfu/splunk-novd2d</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net" target="_blank">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </div></div></blockquote></div> </div></div> <div class="im"> The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at <a href="http://www.partners.org/complianceline" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.</div></div> </blockquote></div>