Can't connect to my SQL server

philjayj · 6 Dec 2008 at 20:48

I'm a bit desperate for some help, and would appreciate any you can give.

I have SQL Server 2005 set up on a spare machine I have on my network. I'm trying to upsize an Access Database and/or create an ODBC data connection, but I keep getting the following message:

Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection.

I have changed the server authentication to mixed, but still no joy.

Oh, and although the SQL Server is installed on a spare machine, its running on a virtual OS.

Thanks for reading.

^^Gord^^ · 6 Dec 2008 at 20:57

Did you restart SQL after making the change to the authenication?

philjayj · 6 Dec 2008 at 21:35

Hi. Thanks for your reply. Yes, its been restarted numerous times but still no change unfortunately.

^^Gord^^ · 6 Dec 2008 at 21:50

Ok, so to check I have this correct. You have a SQL 2005 instance installed on a virtual OS and you are trying to connect to it remotely.

Where are you trying to connect from?
Are both the SQL server and remote device in the same domain?
Are you trying to auth with SA or a Windows account?
Did the error message include a user account or is what you posted the full message?
What version of SQL 2005? Standard / Enterprise or is this the cut down Express?

philjayj · 6 Dec 2008 at 22:05

Hi Gord

Thanks for getting back to me.

I am trying to connect with my laptop on the same home LAN.
I don't have a domain, but they are both in the same workgroup.
I am trying to connect with Windows Authentication.
I am using SQL 2005 Standard.

The error message posted in my previous post is what I'm still getting.

Although when trying to create an ODBC connection, I am unsure whether I should have a tick in "connect to SQL Server to obtain default settings for the additional configuration options." Also, should there be anything in the Login ID / Password fields (even if grayed out)?

Burnsy2023 · 6 Dec 2008 at 22:44

Have you enabled remote connection through named pipes?

philjayj · 6 Dec 2008 at 23:03

I have enabled remote connections via the servers properties, but I don't know about named pipes - how would I check this?

Thanks

^^Gord^^ · 6 Dec 2008 at 23:48

You won't be able to use Windows auth. The PC and server aren't in a domain togeather so in effect don't trust each other.

You will need to use SQL auth (such as SA) to connect or you could go this route http://blogs.msdn.com/sql_protocols...a-workgroup-using-windows-authentication.aspx.

Personally I'd just use SQL auth.

philjayj · 7 Dec 2008 at 00:07

OK, so should I leave the SQL server authentication in mixed mode?

^^Gord^^ · 7 Dec 2008 at 00:12

Yes, you will have to.

morfmedia · 7 Dec 2008 at 08:53

Also worth checking whether the SQL server has an SPN if the machine is in a domain, pretty sure I've seen similar when no SPN was registered....

^^Gord^^ · 7 Dec 2008 at 11:57

morfmedia said:
Also worth checking whether the SQL server has an SPN if the machine is in a domain, pretty sure I've seen similar when no SPN was registered....

He has already said it's in a workgroup.

philjayj · 7 Dec 2008 at 13:40

Gord, using SQL auth works fine. Although I did try the first method mentioned in your link, but that still doesnt work.

Thanks for your help.

Burnsy2023 · 7 Dec 2008 at 13:50

RLBUHT said:
I have enabled remote connections via the servers properties, but I don't know about named pipes - how would I check this?

Thanks

http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=175575&SiteID=1

morfmedia · 7 Dec 2008 at 17:05

^^Gord^^ said:
He has already said it's in a workgroup.

Missed that in the replies.... Ta