CRITICAL: Unable to access SQL Server

[rbaholding]

Hi!

I'm trying to monitor Nagios XI from a database of MSSQL 2008. I use assistants MSSQL Database and MSSQL Server. I write all data requested by the wizard including the port '1433 ', instance, user and password. For testing, I use the database "master".

When the wizard finishes, start checking until the following error for each service: CRITICAL: Unable to access SQL Server.

My SQL server is configured on port 1433. If I run a telnet to the server with the same port, connects properly.

However, if I run the wizard again, leave the field empty port and start checking, appears correct.

Can you help me?

Thanks.

[nscott]

Are you entering a value for both Instance and Port? It should be only one or the other, not both.

If thats not the case I'm going to have to ask you to rephrase your statements as I'm not sure what is being specified at each stage.

[rbaholding]

Just writing the name of the instance, which in my case is 'Instance1'. In other SQL servers, just write the name of the instance but it still shows the same error.

[scottwilkerson]

Usually you need to remote the port for Instance based connections.

While the server may be listening on 1433, this is not likely the real port for this instance.

Additionally, make sure you are using SQL authentication and not a Windows Domain user...

[rbaholding]

Sorry, the problem comes with the user's permissions in SQL Server.
Thanks for everything!.

[maxwellmiranda]

i am using windows authentication...
i am trying to create a user and see if the issue persist.....