My sensor gets a timeout error I believe because its not able to automatically determine the port and I am trying to troubleshoot why.

Article Comments

If no port is specified, the sensor will try to connect to the default port of the server. For Microsoft SQL Server this would be 1433.


May, 2013 - Permalink

Its set to automatic. Presently my SQL server is using port 4113. On my primary PRTG server it negotiates fine but on the failover PRTG server I get a timeout. If I maually set the port to 4113 it connects so I am trying to determine what is stopping the failover PRTG server from negotiating the port.


May, 2013 - Permalink

A little more detail on my question. I have a primary and failover PRTG servers. Each server resides in its own site. The SQL server resides in the site with the primary PRTG server. When the SQL sensor is set to automatic it resolves the port and connects from the primary but the failover receives a timeout. When I manually set the port for the SQL instance then both primary and failover are successful. I think something between the 2 subnets is stopping the failover server from auto negotiating the port for the SQL instance but in order to troubleshoot further I need to understand how that negotiation occurs. Thanks


May, 2013 - Permalink

When the Port Setting is set to automatic the MS SQL Sensor uses the Microsoft SQL Servers default port (1433). Otherwise it uses the port specified by the user. Technically there is no difference between the two connection methods.


Jun, 2013 - Permalink