sql server connect: login failed for user '(null)' -- sql server connect

lange
9/20/2005 7:13:02 PM

sql server connect: My variation of this problem is as follows:
the server has the Windows authentication mode, I'am aware of it so I make
sure I comply with it in my connection attempt (through Enterprise Manager).
I attempt to
connect from another PC. Both the client PC and the server have the same
range of users, same names and passwords. When I connect to an sql server on
a server 2003 box, it works. When I connect to an sql server on an XP box, it
fails (login failed for user '(null)'. I made sure the security envronment is
identical for both (same logins, authentication mode etc). All computers are
in the same workgroup (no domain). When the guest account is included as an
allowable account for the sql server, it connects to the xp box, otherwise -
it fails. And it always connects locally (when I use the local Enterprise

Re: login failed for user '(null)'

Sue Hoegemeier
9/21/2005 7:17:07 PM

Authentication is done using the guest account when simple
file sharing is enabled on XP - you can change it on XP Pro
but not XP home as simple file sharing is always enabled on
XP Home. Refer to the following for more info:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133

-Sue

On Tue, 20 Sep 2005 19:13:02 -0700, "lange"
[quoted text, click to view]

Re: login failed for user '(null)'

lange
9/21/2005 7:30:05 PM

Thanks Sue. Actually I cannot ascertain what mode my file sharing was in,
because
I reinstalled Windows XP, but before I did that I had fixed the problem in a
different
way, although it may boil down to the same: it was about local group
policies. It's not that easily accessible:
you need to run gpedit.msc, navigate to:
Computer Configuration
Windows Settings
Security Settings
Local Policies
Security Options
there is an option there: "sharing and security model for local accounts"
it can be either :"classic" or "guest only". What is needed there is
"classic" of course. If think your solution may implicitly include toggling
this setting and it is easily accessible whereas what I did is not.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server connect group.