Unable to connect to MSSQL datasource over the VPN
Hi,
I've been using the product for over a year and absolutely love it except for this little annoyance. I was never able to get my domain credentials to connect to the MSSQL datasource over VPN on a non-domain joined computer.
So basically from my home computer I have a VPN connection to the office, I can ping the SQL server and there's no firewall restrictions. I can ping the domain controllers as well. I specified a domain user which has admin access on the RDM database, the domain user password, the server in this format SQLSERVER\MSSQLSERVER (we're using the default instance name) and the correct database name we're using. Keep in mind that we use almost the same settings in the office everyday to connect to the same database, we just use the Integrated security instead as we're part of the domain.
With those settings when I click on Test Server I get: Unable to connect to the server!
A network-related or instance-specific error occured while establishing a connection to the SQL Server.
We're using version RDM 10.0.4 & our SQL server is running 2008 R2 64 bits.
Any help will be appreciated. We're a paid a customer so feel free to contact me privately.
Thanks!
edited by exort on 12/2/2014
All Comments (9)
This is a default behavior of MS SQL it only accepts the logged on user of the computer to be the integrated security so this like you see below would not work right off the shell because it only accepts a SQL user into the User field or using the Integrated security (AD).
But you might try a small trick as a workaround that used to work with SQL 2005 have not tried with 2008 and newer.
If you map a drive to the server as the user you want to use, before doing anything then when you connect with integrated security the credentials that you have already established on that server will be used. I used to do this when I was working from a workstation that was not trusted by the domain that the servers were in (SQL 2005). You still only get one set of credentials, this trick won't work for two different sets of credentials.
Regards,
Ingvar Orn Ingolfsson
System Engineer
Axdata AS - Norway
@Ingvar Orn Ingolfsson - Thanks for posting this useful tip.
You can also start RDM with run-as.
More information here: http://help.remotedesktopmanager.com/index.html?tipsandtricks_runas.htm
Regards,
Stéfane Lavergne
@ingvarorn I had hope but just try your map drive suggestion and it didn't work unfortunately.
@slavergne I'm running RDM from my home computer that isn't joined to my company domain trying to connect to the SQL DB over VPN. Therefore, runas with my corporate domain credentials isn't possible.
edited by exort on 12/3/2014
Hey guys,
i have the exact same issue here. Pc which i am working on, is not in my company's domain, so no chance to connect to sql datasource through vpn.
Maybe there is another workaround or anything else to try?
thanks
best regards
Markus
Could you try:runas /netonly /user:domain\username "C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe"
Full article here:
http://codebetter.com/jameskovacs/2009/10/12/tip-how-to-run-programs-as-a-domain-user-from-a-non-domain-computer/
Stéfane Lavergne
Not sure if it will work with a VPN...
Stéfane Lavergne
Hey,
i have tried your mentioned solution, and the /netonly param is the clue :-)
Now it is working on a non domain joined pc even through vpn
thank you very much
best regards
Markus
Markus good to here, thank you for the update.
Regards,
Stéfane Lavergne
Hi
The runas with the netonly parameter is described in http://help.remotedesktopmanager.com/tipsandtricks_runas_manualrunas.htm
Best regards,
Maurice