3

I have two local SQL Server instances running on my local machine. The first is SQL Server 2008 R2 Enterprise Edition (named MSSQLSERVER) and the 2nd is SQL Server 2012 Business Intelligence Edition.

My problem is with SSMS 2012 which can connect to distant servers but not the local 2012 instance; I can however connect to this instance from SSMS 2008.

The error message I get when trying to login is

Login Failed. The login is from an untrusted domain and cannot be used with Windows Authentication. (Microsoft SQL Server, Error: 18452)

I must point out that I don't have the necessary privileges to access SQL Server Configuration Manager (blocked by group policy).

Any help would be appreciated.

Improve this question
9
  • Did you try connecting using SQL auth instead of Windows auth?
    – Aaron Bertrand
    Commented Jun 3, 2013 at 21:38
  • @AaronBertrand I did try that but it didn't work.
    – Ibrahim Mezouar
    Commented Jun 4, 2013 at 9:05
  • 3
    And did you get a different error message?
    – Aaron Bertrand
    Commented Jun 4, 2013 at 11:30
  • @IbrahimMezouar Have you solved the issue? I'm afraid that if you don't respond to the questions in the comments, the question will be closed.
    – ypercubeᵀᴹ
    Commented Jul 5, 2013 at 13:48
  • I'm sorry, I missed the last comment. I have not solved the issue yet.
    – Ibrahim Mezouar
    Commented Jul 8, 2013 at 19:12

1 Answer 1

Reset to default
-1

I saw an item on Pinal Dave's blog recently that may answer your question. He suggests adding the line 127.0.0.1 localhost to your hosts file

The full article can be found here

I do note, however, the situation he refers to is a machine that is not part of a domain - if your machine is, then this may not solve it

Improve this answer
3
  • Also this will only help if you are accessing the instance using the explicit name LOCALHOST\instance name.
    – Aaron Bertrand
    Commented Jun 3, 2013 at 21:52
  • 7
    I am not sure I buy Pinal Dave's explanation. If he was trying to access the IP address 127.0.0.1, adding that entry to the hosts file does nothing - the hosts file is used to resolve names to IP addresses, not the other way around.
    – Aaron Bertrand
    Commented Jun 3, 2013 at 21:55
  • I tried this but it didn't work. but if the problem really lies within the hosts file, how come SSMS 2008 can connect to both instances? (2008 and 2012) I reiterate, I'm having this issue only with SSMS 2012.
    – Ibrahim Mezouar
    Commented Jun 4, 2013 at 9:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.