Sql-server – With SSMS on the local machine, is it possible to login to a remote SQL server on the VPN network via the Active Directory credentials

active-directoryloginssql serversql-server-2016ssms

I'm trying to login to a SQL server on my work network with a VPN connection to the network and by using my AD credentials.
When I'm directly on my office machine, I use "Windows Authentication" as the Authentication method in SSMS and that works fine.

When I'm VPN'ed onto the network and using my local machine, Windows Authentication doesn't work (understandably) but if I try to use the "Active Directory – Password" Authentication method (I was hoping I could put in my work's AD account to connect to the remote server) I get the following error:

It sounds like it can't find the server, but when I ping the server from my local machine, I'm getting a response.

Note: "Allow remote connections to this server" is checked.

Best Answer

As I said in my comment, I do not fully understand what your issues are.

But I think the solution is to open SSMS as another user.

Personally I have the SSMS icon in my task bar:.

Shit + R click
Select "Run as a different user"
Enter the account and password you would normally use on your office machine.

SSMS will connect to instances as if you where on your office machine and had opened SSMS.

Note I assume you are working remote for possibly the first time. There are a number of security barriers, that your organization may have in place to prevent you from connecting from home. I can't address those, and this is probably not the site to address them.

Related Solutions

Sql-server – Connect to SQL Server using windows authentication from another PC without Active Directory

If none of the machines involved have Active Directory authentication enabled via Kerberos, which precludes using an online-based Microsoft Account (Windows 8 and higher), you should be able to connect to SQL Server using Windows Authentication assuming you follow these points:

Ensure SQL Server is configured to use TCP connections.
Ensure the Windows firewall is either disabled or has SQL Server connections allowed.
The machine where SQL Server is installed needs Windows user accounts for all the people who will be connecting via the network. For instance, if the SQL Server computer is named MyPC, and you have User1, User2, and User3 who will be using the SQL Server, MyPC must have accounts setup for User1, User2, and User3 with the same password those user accounts use on their own PC.

You create logins in SQL Server for those user accounts, i.e.:

CREATE LOGIN [MyPC\User1] FROM WINDOWS;
CREATE LOGIN [MyPC\User2] FROM WINDOWS;
CREATE LOGIN [MyPC\User3] FROM WINDOWS;

The client machines may need to connect to the server using the server's IP address instead of it's name. If the server's IP address is 192.168.0.100, and it is listening on port 33333 then they would use this as the server name to connect to:
```
tcp:192.168.0.100,33333
```

If you follow all the above advice, then receive the following error when connecting, then the client PC is using Kerberos authentication, and nothing will help you connect.

The target principal name is incorrect. Cannot generate SSPI context.

SQL Server – Is Password Complexity Policy Linked to Active Directory?

As far as I know, as long as the users have been created with CHECK_POLICY they will inherit it from the domain.

If not, you'll have to enable the policy use for all of them. Or use SQL Server 2012 BPA, as it has a check for this part (2).

The security policy might be set in Windows, or might be received from the domain (1).

https://msdn.microsoft.com/en-us/library/ms161959(v=sql.110).aspx (1)

https://support.microsoft.com/en-us/help/2028712/understanding-password-policy-for-sql-server-logins (2)

Best Answer

Related Solutions

Sql-server – Connect to SQL Server using windows authentication from another PC without Active Directory

SQL Server – Is Password Complexity Policy Linked to Active Directory?

Related Question