Error connecting in Management Studio

Hello,

I am having problems connecting to my SQL Server instance with Management Studio; basically the setup is as follows;

*Single server running windows 2003 enterprise - in a workgroup not domain
*SQL Server is installed on this machine
*When I try and connect from the same machine using its own IP address and Windows authentication I get the 18452 error "login failed for {NULL} user"

I am testing it like this because Sharepoint is failing in configuration wizard because it is connecting the same way - at least the login failure audit logs say the same.

Many thanks for answers

With which application are you trying to connect ? Did you try another application yet ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

This commonly happens with trusted authentication when your local user does not translate to the other machine (e.g. LOCAL_SYSTEM or NETWORK_SERVICE, etc.). Naturally, if you translate to the IP address, even on loopback, the account must be one that can be understood remotely, so in this case your client and server are the same machine, but the same truth applies. Your user must be recognizable from a remote connection to this machine. Try rasing into the machine from a remote machine under the user account to see if it works. If it doesn't ras, your user needs to be reconfigured/reselected.

http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/ias2000a.mspx

http://ablog.apress.com/?p=1127

http://support.microsoft.com/kb/215383

http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/kerberos.mspx

It could also be possible that your machine is not running the correct authentication protocols to support Trusted authentication on your OS. I don't actually know how to configure users/authentication on Windows workgroups/domains so how this is addressed is beyond me.

Hope that helps,

John

|||Thanks for the response John.

The user I am using is the default "Administrator" (I know bad practice) for testing.

It is definatly something to do with the user not being understood in the loopback.

However like you, I have no idea how to fix this :/

Cheers
|||Try a different user or modifying your administrative user to have remote access. Administrator is one of those users that is traditionally a local account only. Optionally, you could try fiddling with the user manager and enabling remote access for the administrator account, but I am fairly certain that would open you up to some evil attacks.|||Can you tell us how you connect exactly?
Are you using OPENROWSET?