Using ADDM v8.1, with TKUs all up to date to July 2010. Goal is to to discover Database names of our 170~ Microsoft SQL Server instances.
We had a local account created on one MS SQL instance with read-only access. Added the credential to the UI and it worked.
It seemed sensisble to see whether we could use our Active Directory account (“corp/svc-cc-tideway”) to connect to MS SQL. To check if it were possible, I manually logged into a server (different to the one above), opened MS SQL Management Studio, connected through Windows Authentication and ran the show databases query; this worked.
I then added “corp/svc-cc-tideway” to the MS SQL credential list on the ADDM UI, for the time being specifying it for just the IP address and port number of the server I manually logged into. Running a test (and rescans) gave the following error…
SQL Provider: Unable to open a connection to the database: Login failed for user ‘corp/svc-cc-tideway’.…regardless of whether I left the password field blank or with the password entered on the credential (when I logged in using Windows Authentication on the server itself it just required I click ‘Connect’ rather than enter the user/password again).
Does this mean that the only way to connect to MS SQL Server instances is through local accounts on each instance or have I potentially not exhausted another way of doing this?
Just wanted to double-check as using one single username and password for this seems a more sensible approach to having 170 local ones created.