Joined: 05 Jun 2009
|Posted: Wed Mar 07, 2012 4:57 pm Post subject:
SQL Monitor will try to connect from the machine running the 'base service' (which can be different from the one running the web app).
From the the machine hosting the SQL Monitor base service, see if you can ping the fully qualified domain name of the production server. If it doesn't resolve, SQL Monitor won't be able to see it either. If it does work, then ensure that access to each of the production machine's TCP/UDP ports is possible (for reference: this article on firewalls enumerates the ports that SQL Monitor requires open).
If you can fully access the production machine from the base monitor's host and can confirm that SQL Monitor is still failing when using the fully qualified domain name, then I would suspect that the user account SQL Monitor is running as (e.g. LOCAL SERVICE) is connecting to the production machine using an anonymous connection. In this case, you can override the machine credentials from the UI. Note that SQL Monitor needs both access to the OS and SQL Server, and these credentials can be separately overridden.
What is the error message in the UI when you try to add the production server in Configuration > Monitored servers?