November 8, 2009 at 8:04 pm
I've got two SQL 2008 named instances installed on separate computers. (One of these is a VM.) Both instances are on the same domain. The only difference that I can find between the installations is the the one on the stand-alone computer is installed and run with a domain\administrator account, while the VM is installed with a domain\service acct.
When I attach to the domain via VPN, and run SSMS from my Vista workstation, I have no problem connecting to the stand-alone computer with Windows Authentication. However, when I try to connect to the instance installed on the VM, I get this message:
Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Microsoft SQL Server, Error: 18452)
I can log into this server from my workstation with SQL Server Authentication.
If I RDP into the server, I can log in with SSMS on that computer w/ Windows Authentication.
I've researched this error for about a week on the internet, but I can't find anything that fixes this issue. Most suggest going into mixed authentication, but I already am in that mode.
All help gratefully appreciated!
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
November 9, 2009 at 9:01 am
What VPN client are you using?
You might want to check to see if the one with the problem has SPN's setup correctly.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
November 9, 2009 at 9:34 pm
Jack Corbett (11/9/2009)
What VPN client are you using?
We've been using "The Greenbow VPN", but are shifting to "OpenVPN". Both are having this issue.
You might want to check to see if the one with the problem has SPN's setup correctly.
We'll research and look into this (might take a few days; this is for the evening gig), and get back.
Jack, thanks for replying.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
November 10, 2009 at 1:00 am
Dear,
The issue is not related with VPN. It is with authentication. so. try with a trusted connection string attribute.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply