[dba-SQLServer] Back to the login thing

John W. Colby jwcolby at colbyconsulting.com
Thu Nov 18 10:29:36 CST 2004


Eric,

Well that is the confusing thing here.  Every one of these three machines
has an administrator account (user name Administrator) all with the same
password.  I log in as that user on all the machines.  Each of these
Administrator accounts is indeed an administrator on that machine - these
are the default admin accounts created by Windows as Windows is installed on
the machine.  

So AFAICT I have done exactly what you are discussing.  

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 Eric Barro
Sent: Thursday, November 18, 2004 11:07 AM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer] Back to the login thing


John,

If you're using Windows authentication you just need to make sure that you
have the same account on each machine and then add that user under the
Security section (Login) of SQL server. Create the login that will be the
basis for the user for the database. Basically you mirror the Windows
account into the SQL server Login account and create users off of that
Login. To make things simple just make it a one-to-one relationship.

But in order for any machine to have access to other machine's resources you
will need to set up the same account on each machine with the same user/pwd
combo and same rights/privileges especially if you are not operating in a
Windows domain environment with one server as the primary domain controller
managing the Active Directory.

Eric

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W.
Colby
Sent: Thursday, November 18, 2004 6:26 AM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer] Back to the login thing


Andrew,

While I am the only user of this db ATM, in the near future the owners of
the database expect to be able to use it in some undetermined manner.  I do
not know yet the "how" of the access - it will probably be a mix of web
server, remote access and / or vb.net application.  In any event I have read
(and as you are well aware I am totally ignorant on this stuff) that using
windows authentication is more secure.  I am therefore making every effort
to get this set up from the gitgo to do that so I don't have a "gaping
security hole" hanging out there forgotten.

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 Haslett,
Andrew
Sent: Wednesday, November 17, 2004 11:11 PM
To: 'dba-sqlserver at databaseadvisors.com'
Subject: RE: [dba-SQLServer] Back to the login thing


As we've suggested multiple times, why are you using Windows Only
Authentication?

If this is just an internal system, then there's no need.  Just set up some
accounts using SQL Authentication on the other boxes and connect to it using
this username and password.  Presto. You're done. 

-----Original Message-----
From: John W. Colby [mailto:jwcolby at colbyconsulting.com] 
Sent: Thursday, 18 November 2004 1:04 PM
To: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer] Back to the login thing

I really need to get query analyzer able to run on Neo2 SQL Server from all
of my workstations.  I have gone through the systems setting security on the
servers to Windows only / System Account.  EM is now able to see Neo2 Server
from all the workstations, and can in fact browse the tables, open the main
table and return records etc.  

QA however fails at the login with a consistent "Login failed for user
'Neo2\Guest'".  Msg 18456, level 16, state1.  On Neo1, Neo2 and Soltek1 I am
logging in to Windows as Administrator with an identical password on each of
those three machines.  I can use QA on Neo2 but I cannot use QA on Neo1 or
Soltek1 against Neo2.

Can anyone help me figure this thing out?  I REALLY need to get all my
workstations banging queries against SQL Server on Neo2.

John W. Colby
www.ColbyConsulting.com 

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


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com

IMPORTANT - PLEASE READ ******************** 
This email and any files transmitted with it are confidential and may 
contain information protected by law from disclosure. 
If you have received this message in error, please notify the sender 
immediately and delete this email from your system. 
No warranty is given that this email or files, if attached to this 
email, are free from computer viruses or other defects. They 
are provided on the basis the user assumes all responsibility for 
loss, damage or consequence resulting directly or indirectly from 
their use, whether caused by the negligence of the sender or not.
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com




_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com








----------------------------------------------------------------
The information contained in this e-mail message and any file, document,
previous e-mail message and/or attachment transmitted herewith is
confidential and may be legally privileged. It is intended solely for the
private use of the addressee and must not be disclosed to or used by anyone
other than the addressee. If you receive this transmission by error, please
immediately notify the sender by reply e-mail and destroy the original
transmission and its attachments without reading or saving it in any
manner..  If you are not the intended recipient, or a person responsible for
delivering it to the intended recipient, you are hereby notified that any
disclosure, copying, distribution or use of any of the information contained
in or attached to this transmission is STRICTLY PROHIBITED. E-mail
transmission cannot be guaranteed to be secure or error free as information
could be intercepted, corrupted, lost, destroyed, arrive late or incomplete,
or contain viruses. The sender therefore does not accept liability for any
errors or omissions in the contents of this message, which arise as a result
of email transmission. Users and employees of the e-mail system are
expressly required not to make defamatory statements and not to infringe or
authorize any infringement of copyright or any other legal right by email
communications. Any such communication is contrary to company policy. The
company will not accept any liability in respect of such communication.


_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com







More information about the dba-SQLServer mailing list