SQL monitoring: CRITICAL:Unable to access SQL server

[shannon]

I am trying to monitor a SQL Server 2012. The server uses sa crudentials, so I am using that for the DB connection.

When I telnet to the SQL server on port 1433 I get a blank screen, indicating the port is not being blocked.
I am able to login to the SQL server from command prompt on SQL server using SQLCMD -U sa -P sapassword

Any ideas?

[lmiltchev]

When you ran the wizard, did you enter a value for both Instance and Port? It should be only one or the other, not both.

[shannon]

Thanks for the tip. I was inputting values for both instance and port #.

When I just put in a port number, i get NULL values.
When i input the instance name, I get cannot connect to database.

Im happy to just use the port number, since its connecting to the db. Any ideas as to why the NULL value is appearing?

[lmiltchev]

Can you show us the actual command that you are running from the command line? Hide the sensitive data.