basic windows authentication problem

From: Tony Su (tonysu@su-networking.com)
Date: 12/19/02


From: "Tony Su" <tonysu@su-networking.com>
Date: Thu, 19 Dec 2002 09:31:23 -0800


Others may have more to say, but IMO the problem is
basically that you're running XP Home on your workstation.
XP Home cannot join a Domain, so every time you connect to
a database, you will be presenting either security
credentials stored locally on your machine or SQL
Username/Password. You cannot present Domain credentials.

So, your solution should be to either login with SQL
credentials (and configure your dB to support Mixed
Authentication) or upgrade your workstation to XP Pro
(highly recommended).

I'm somewhat surprised you have any kind of access to the
database already... speculating that you may have Mixed
Authentication turned on already and/or you might have
Ownership permissions due to creating the dB.

Tony Su

>-----Original Message-----
>Hi all,
>
><Newbie alert>
>
>I've got a simple setup here for getting to grips with
SQL Server 2000, but
>can't connect to the sample database from my PC.
>
>Existing network had a single Win2K server, called
SERVER1, with Active
>Directory domain COMPANY.
>I have created an account FRED.
>My PC, called PC1, runs XP Home, with an account also
called FRED.
>Both accounts use same password, so when I log in on PC1
as FRED I get
>access to all areas available to FRED on SERVER1.
>
>Added new Win2K server SERVER2, which joined the COMPANY
domain. I can log
>in to this server as FRED (or any other valid COMPANY
account) without a
>problem.
>
>I have run
> exec sp_grantlogin 'COMPANY\FRED'
>on SERVER2, and this granted login access ok. Logging in
as FRED directly on
>SERVER2 allows me to run Query Analyser with no problems.
>
>In Query Analyser on PC1, logged in as FRED, connecting
to SERVER2 using
>windows authentication, get the error 'Login failed for
user (null)'.
>
>Seems as if the SQL Server does not recognise my account
as being
>COMPANY\FRED....
>
>If I try to map a drive on PC1 to SERVER2, it initially
tries to use
>PC1\FRED as the account name, which fails until I change
it to use
>COMPANY\FRED . Is this what is happening when I try to
connect to SQL
>Server?
>
>Is this a problem with my SQL Server setup, or is my
basic network
>authentication setup wrong? Is the way I use the same
account name on my XP
>box and on the server the cause of the problem?
>
>Any suggestions?
>
>TIA,
>
>Ian
>
>
>.
>



Relevant Pages

  • Re: Compromise?
    ... Yes, if you don't provide a password on your SA account, anybody able to run ... and connect now has complete control over your SQL Server. ... Server has. ...
    (microsoft.public.sqlserver.security)
  • Re: Windows Auth to SQL Server from ATL Web Service not working...
    ... account I'm logged on as. ... SQL on a different box from my web service in an Atl Server web ... impersonation token is not passed on to the SQL Server. ... Event Category: Account Logon ...
    (microsoft.public.vc.atl)
  • Re: Discussing 3 different strategies for deleting from multiple tables
    ... I will be using SQL Server but I am riding on top of a third party ... FYI, Account contains around 20K ... >>> This results in one parameterized query followed by two more trips to ...
    (microsoft.public.data.ado)
  • RE: connection problems in secondary site and SQL server
    ... Do you have a Windows 2003 server anywhere in your environment? ... i can't add this account to this group. ... SMS Management Point encountered an error when connecting to its Database ... SMS on SQL Server My_Primary_SMS_Server. ...
    (microsoft.public.sms.admin)
  • RE: MP Install issue
    ... Will setting the SPN on the domain account fix the communication issue ... >> MPDB ERROR - CONNECTION PARAMETERS ... >> with a trusted SQL Server connection. ...
    (microsoft.public.sms.setup)