unable to user domain credentials for MSSQL server
I am working on getting a MSSQL database up and running as a central repository for Remote desktop Manager.
The problem that I am having is setting up the data source within RDM.
If the computer is one the domain, I can use integrated security to log into the data source. This process works, and I have added some users to the new data source and added a few sessions, and linked them to security groups etc.
The Problem that I am having is that if the computer running RDM is not connected to the domain. and I try to connect to the central datasource, rather than using integrated security I have to type in a username and password.
at which point I can't log into the data source.
It seems to be an issue with the username and password option within the SQL server datasource setup itself.
I tried on a computer that was working with integrated security. I changed the datasource option to a username and password and it gives an error even though it is the same user that is currently logged into the computer.
I have tried typing domain\username and username@domain, I even tried domain2000name\username and username\domain2000name.
none of these options worked, can you please help.
All Comments (3)
Hi,
I think that the only solution is to use SQL Server in mixed mode and use a user without the Integrated Security:
http://technet.microsoft.com/en-us/library/ms144284.aspx
David Hervieux
I see, it is a Function of MSSQL server not being able to pass any credentials to an authentication source. If I want to be able to log in, I Need to place my username and password into the MSSQL server.....
HOWEVER... I did some searching online after figuring that out and found this.
runas /user:mydomain.local\username /netonly "C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe"
If you run this command, it will open a prompt that will ask for your password, and authorize you, and run the program as that user, which you can then use integrated security option to pass that token through SQL server.
NOTE: this only works if your computer knows how to find the Active directory of the domain you are trying to use.
Thank you very much. It's a good workaround
David Hervieux