[dba-SQLServer] Back to the login thing

Jim,

I followed you (I think) until I got to 

>Navigate to the X:\windows\security\database\ directory and select the
latest *.sdb .

I assume that is the windows directory.  I went there and found two
databases.  Secedit.sdb denies my attempt to open it.  Udated.sdb allows me
to open it but it cannot be expanded per your next instruction.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Jim
Lawrence (AccessD)
Sent: Thursday, November 18, 2004 2:16 AM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer] Back to the login thing


Hi All:

XP is a 'bastard' of an OS when it comes to security. Unlike all previous
systems, it has a new method of handling security access, to a station. The
default mode is the 'guest' mode and it has screwed up more uninformed users
and technical support the possibly imagined. There is a way to fix this and
that is by changing the security method to 'classic' mode but it is
carefully hidden. Below are steps to resolve this: (You have to be logged on
as administrator and have access to the WINNT directories and below.):

1. Go to <start> and enter 'mmc' in the <run> field.
2. When the MMC menu pops up select File/Add/Remove Snapin... 
3. Select Add on the Add/Remove menu. 
4. Select 'Security Configuration and Analysis' from the list menu.
Highlight, Add, Close and OK. 
5. At the 'Consul Root' menu, right-mouse click and select 'Open database'. 
6. Navigate to the X:\windows\security\database\ directory and select the
latest *.sdb . (Usually 'update.sdb') 
7. Expand the 'Security Configuration and Analysis' icon, 'Local Policies'
and 'Security Options'. 
8. From the right list double click 'Network Access: Security Model for
Local Accounts'. 
9. Tag 'Define this Policy in the database', choose 'Classic - Local users
authentication as themselves', Apply and Exit.

Now you should not have any issues connecting to your SQL now.

HTH
Jim