|
|
|
|
|
Database Scanner 3.0.1 1 2 3 4 5 6 7 8 9 10 After you have setup your security policy, you are ready to scan your systems. Clicking the Scan Database from the main workplace will display the screen below. You can add multiple servers to scan in a single run and then analyze the output. For simplicity, I scanned a single 7.0 server that was installed with all of the defaults. The only changes to the defaults were that it was running under a named NT account and a login called test with a password of test was created. (I also had setup merge replication between two databases.) Due to the maximum security policy that I scanned with, this should have produced several security failures. In the grid to scan the servers, I selected to use a trusted connection since that is how I connect to all of my servers even though they run in mixed mode.
Click the Start Scan button and...Whoops!!! I'm logged in as an Enterprise Admin (Win2K) and I can successfully get a trusted connection from this workstation using Enterprise Manager and Query Analyzer. Command line isql also works with a trusted connection. So, this was very puzzling. After going through the doc, I finally had to send a message to tech support. It seems that I can not get a trusted connection within Database Scanner unless I am running multi-protocol. This is a very irritating feature since multi-protocol has never been a requirement to create a trusted connection. I've run almost predominantly TCP/IP for the default net lib along with named pipes and I have always been able to get a trusted connection. Database Scanner imposes a login restriction that doesn't exist in any other product I've worked with. I would classify this one as a bug. So starting over, you will need to input the sa password to get a scan to run. Running under strictly integrated security? You'll have to add the multi-protocol netlib to your server and workstation in order to run Database Scanner.
|
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.
