SQL Server Management Studio 2008 Runas User on Different Domain Over Vpn

SQL Server Management Studio 2008 Runas user on different domain over VPN

Try this:

NET USE \\DBSERVER /USER:DOMAIN\USERNAME

You will be prompted for your password. This establishes a NetBIOS session with the database server. You should be able to see the shared folders and shared printers on the database server once you have done that.

If that works you should be able to connect using SSMS as yourself. You may have to specify "named pipes" as the network protocol to usem, if it doesn't work with TCP (but I think it will).

• Menu->File->Connect Object Explorer...
• Options->Connection Properties->Network protocol
• Specify "Named pipes"

Named Pipes inherits your existing NetBIOS session, so provided you can list the shares you are probably good to go.

Update: It looks like in some configurations this does not work with TCP connections, (possibly due to some security update). In these cases you should enable Named Pipes, and set named pipes in your connection string.

Can't connect to SQL Server in different domain using SSMS and Windows 7 Credential Manager

It looks like there is a bug in the Windows 7 Credential Manager that causes this behavior. After lots of Internet research, I found some ugly workarounds, but also found a great one:

In Credential Manager, add an entry for the remote server, but instead of adding just the server name, like database.contoso.com, add the server name with the SQL Server port, like so:

database.contoso.com:1433

This results in the desired behavior, with no pain!

Source: http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/c05a90e4-cb16-46f6-9072-37083c65696d/

Also remember, of course, that you need to prefix the remote username in Credential Manager with the remote domain name, like so:

database\administrator

connect to sql via windows authentication over vpn

Try creating a shortcut with:

runas /noprofile /netonly /user:domain\username ssms.exe

You may have to hard-code the path to ssms.exe. On modern versions, that's:

"C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe"

In a few locations it will look in SSMS like you are using your local credentials, but you should be able to verify on the remote server that your credentials are being passed, e.g.

SELECT SUSER_SNAME();

This of course depends on your requests being correctly routed to the destination SQL Server.

SQL Server 2008. I created an instance of SQL Server. My user domain has since changed. How do I reconfigure SQL for my new user domain?

Sql server is 'nothing' more than a windows service. By owner of instance, perhaps you mean the account under which the ms sql server service is running? If so, manage computer, services, choose the service with the instance in question, set the logon name & password.

• Changing the service account
• I just plain don't like this answer here --> Experts Exchange
• If you just like learning stuff, you might enjoy this one: NYC DBA

Your .Net apps --> depends on "how" they are configured now. If they are on the same box and were using something like (local), nothing need be changed. If they were configured to point to the machine name, such as machine.old_domain.com, then simply changing them to machine.new_domain.com. If they are configured to point to machine and the name of the machine didn't change, no configuration changes needed.

This are just starter answers. I've never had this happen to me. Good luck my friend.

How do I authenticate to a SQL Server database on a domain from a virtual machine off the domain?

You can run Visual Studio (or SQL Server Management Studio) as the user on the domain. The trick is, you have to use the “/netonly” option of the “runas” Windows tool, so that you can run as a domain user on a non-domain machine.

Namely, in a command prompt you run this command (filling in your own criteria):

runas /netonly /user:<Domain>\<User_Name> "<Your_Program.exe>"

Alternatively, you can create a shortcut on your desktop, and set this command as the shortcut target. Upon running the shortcut/command, you enter your credentials when prompted and visual studio (or whatever program you like) will run as the domain user.

Build SQL Connection string with integrated security for use over VPN?

The VPN is a red herring. The issue is that the user is not logged in under the same domain as the SQL Server. The same issue would arise with any non-domain-joined PC, whether on a VPN or not.

1. You could join the PC to the domain. This is the best solution.

2. You could use the Legacy method - create matching usernames and passwords. However you then need to make sure they stay in sync.

3. You could use the NET USE command or NetUseAdd API to log in to the domain after connecting to the VPN.

See this question for more:

• This is the best one for you to use: SQL Server Integrated Security

• But see also this one: SQL Server Management Studio 2008 Runas user on different domain over VPN

---

Related Topics