Jay has been busy setting up Imperva to lay the foundation for tighter Security auditing of our database servers.
The DB/2 and Sybase work has been in place for years.
As always it is SQL Server that it is coming up the rear end.
Rather than go with SQL Authentication we chose to go with Active Directory accounts.
Here is a brushed-up screen shot…
Default Database Connection
- Username :- lucy
- Password :- abrams
- Verify Password :- abrams
- Named Instance :- <leave blank> as it is a default instance
- Port :- 1433
- Domain Name :- LAB
Couldn’t establish database connection to MsSql service at IP z.y.x.w, Port 1433: Login failed.
The login is from an untrusted domain and cannot be used with Windows authentication.
Please verify configuration, and that you have saved your changes, then try again.
Went to a MS Windows Machine, logged in with a good account.
Tried out the dedicated account we had set up for Imperva.
Command looks like…
runas /user:LAB\improvise cmd
Launched Computer Management and tried adding AD Account to the User’s Group on our test machine.
Determined that the AD Account setup was actually something else.
Thanks goodness that it is a simple incorrect AD Account.
Have too much going on to add on Active Directory Forest & Trust relationships and Network Firewall.