Add SQL Target: unable do resolve network location

Hey,

There are some steps you can try in this post (the same error message was flagged):
https://support.sentryone.com/s/question/0D54N00002u5hVHSAY/how-do-i-add-an-external-sql-server-not-on-a-domain

If this doesn't work, can you send me a DM with your email address and I can get someone to reach out.

Kind Regards,

Owen

Hey there Rafael-

If you're able to connect via SSMS from the same machine using the same credentials, then the issue is likely with the host discovery part of the connection tests.  Can you try running Steps 2-9 from this post and see if you're able to connect via WMI?

https://support.solarwinds.com/SuccessCenter/s/article/Testing-WMI-Connectivity?language=en_US

If you receive any errors messages during this test, you'll want to verify the following on the target machine:

• The account being using for the Monitoring Service is part of the Administrators group on the host
• The Remote Registry service is started
• The Windows Management Instrumentation (WMI) service is started
• All the necessary ports for WMI are open, which can be found at https://docs.sentryone.com/help/performance-analysis-required-ports.

Let us know how it goes!

Hi.

I'm experiencing the same issue.

I have two non-domain servers; a transactional instance and a replicated MI instance. I am installing SQL Sentry on the MI instance to monitor the transactional instance.

When connected to the MI instance and running SSMS I can connect to the transactional instance without any issue. When I try to connect with SQL Sentry, I get an error:

---------------------------
Connect to Target Failed
---------------------------
We were unable to connect to this Target. The additional information below may help in resolving the issue.

Additional Information: Unable to resolve network location.
---------------------------
OK   
---------------------------

So far:

• As mentioned above, connecting with SSMS works absolutely fine.
• I have carried out the wbemtest.exe check described above and this passes.
• I have tried to connect using an instance name or IP address but neither work.
• I can not telnet using port 1433 so am using the listening port 54916. 54916 works in telnet.

Any support gratefully received!

Thanks.

MK

Interestingly, I have just deliberately changed the password to be wrong and can see a failed login on the transactional instance. Even more confused as the error suggests a network related problem but it is clearly hitting the server.

MK

Hey there selwonk11 !

I'd recommend opening a case with Support and they should be able to work with you to resolution.