Do we need to open port 1433 for MS SQL discovery

moresr
Giga Contributor

Hi All,

I am discovering windows servers, Observed that mssql instance is created but not getting other attributes like version, edition, service pack, db catalog etc is not populated.

All windows server attributes data fetched successfully without any errors.

When I checked with DBA team , they are saying these servers are behind firewall.

So just want inputs is it necessary to open firewall ports for 1433 port rom MID server to SQL servers. I don't see anywhere mentioned in SNOW documentation?

Thx

SRM

8 REPLIES 8

doug_schulze
ServiceNow Employee
ServiceNow Employee

You do not for we do not query the DB directly.. its through a remote powershell script thats executed through the OS...However, you do want to be sure you have all the Microsoft SQL Servers - ServiceNow Wiki requirements in place for success...


Thanks Doug for quick response.


For few servers for which discovery is failing to get data I have observed error "Authentication failure with the local MID server service credential." in Sql powershell .


Is there any way to find out why it is failing or any alternate way to check credentials provided will work for sql discovery.



Thanks.


doug_schulze
ServiceNow Employee
ServiceNow Employee

That I do not know..that error is just that, the script isnt working against that DB.. What I do in that case is have folks compare one that works against the one that doesn't and identify what is so different about your user between those two instances...a good DBA can be of tremendous service here..


aaron_dart
ServiceNow Employee
ServiceNow Employee

If you have access to a helsinki instance export and import the sqlinfo.ps1 powershell script in the instance having the issue. There is one PRB where if the mssql named instance is not listening on default port 1433, it will not discover mssql instance version, db catalog, etc information. You can use the sqlinfo.ps1 from Helsinki. I have not been able to use any sqlinfo.ps1 from any Geneva release that fixes the issue so far.



I forgot to add this:


discovery_probe_parameter.do?sys_id=de07453f0a0a0b7800d06b79122bbc5b