Right-click on the database in question in the object explorer and select "New Query".
Buck Woody
Right-click on the database in question in the object explorer and select "New Query".
Buck Woody
Right-click on the database in question in the object explorer and select "New Query".
Buck Woody
(Cross post from newsgroup)
Attempting to implement Windows authentication between trusted domains. . .
I have a domain trust set up between two domains connected via persistent vpn:
REMOTE and HQ
sqlserv is: HQ\SQLSERV (SQL 2000 server)
client machine is: REMOTE\MACHINE1 (SQL 2005 tools)
I sucessfully added user REMOTE\User1 to system admins on HQ\SQLSERV I can login via Remote Desktop from REMOTE\MACHINE1 to HQ\SQLSERV and open SQL2000 Query Analyzer and query databases as REMOTE\User1
When running SQL2005 SQL Server Management Server on REMOTE\MACHINE1 logged on as REMOTE\User1
I cannot connect to HQ\SQLSERV.
I get:
TITLE:
Connect to Server
Cannot connect to HQ\SQLSERV.
ADDITIONAL INFORMATION: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476
BUTTONS: OK
Any ideas? What I am trying to do should be possible. Isn't it?
Check your connection info in SSMS on REMOTE\MACHINE1Mulhall wrote:
Check your connection info in SSMS on REMOTE\MACHINE1
Check you have all the required DNS
Try osql -SSQLSERV -E
same error|||
Ahhh. . .
found the problem. . .
forgot that we had moved all of our workstations into sets of ADS folders, one for general all purpose use where access via network was permitted to all authenticated users and one set that had access permissions specifically defined to only developers.
Had to give access to the remote developers group via group policy.
The easiest thing was -
Add a Local Domain Group on HQ - Remote Developers
Add REMOTE\Developers to HQ\Remote Developers
Add HQ\Remote Developers to 'Allow access from network' on the applicable gpo
Does that make sense?
Well, it works!!!
You know. . .
Somethings M$ does really really well - Active Directory/Policy Management/Name Service Administration, SQL Server!!!
Somethings they choke on - Visual Studio 6 (oh what a dog!)
At any rate, setting up this VPN and Domain trust was rather simple and straight forward!
I just upgraded my 2000 installation to Sql Server 2005 Developer. When I try to create a new login I can only use local accounts. Search and the Locations only displays the computer name and not the domain. Any help would be greatly appreciated,
Robert van Poelgeest
Hi Robert - I assume you are using SSMS but correct me if I'm wrong.
Are you running SSMS (client) on the same machine as the Server?
Are you logged into client machine with a domain account from domain you want to add?
Can you add the desired domain account using the CREATE LOGIN command?
|||
Hi Bruce,
Yes I am using SSMS on the server itself and yes I am logged in using a domain account. I haven't tried using a CREATE LOGIN account but I will.
update: This whole problem was caused by a dns configuration problem and was not caused by anything in Sqlserver
I have a situation that I have discovered in our QA database that I need to resolve. When I looked at the Activity Monitor for our server, I discovered that a process is running under a domain user account for one of our .Net applications. The problem is that that domain user account has not been created as a SQL login account on the server. I am trying to figure out how someone can log in to the database server with a domain user account that has not been added to SQL Server as a login account.
Does anyone have any insight on this? I don't like the idea of someone being able to create domain account that can access the database without me granting them specific access.
- Larry
It could be working under the guest account, it could be included in a domain group account that has database access, it could be under an ALIAS (a deprecated feature -and still dangerous).|||Most likely the Windows user has permission to connect via a Windows group membership. If the user belongs to one or more of such group and it has CONNECT SERVER permission, the Windows user will have access to connect to SQL Server.
-Raul Garcia
SDE/T
SQL Server Engine
|||Apparently, the account in question was a member of the WIndows local admin group. It makes me rather nervous that an ID could be created that basically has unlimited access to my databases and, as the DBA, I can't do a whole lot about this. Is there a good way that I can mitigate this risk?
|||Here is a link to a different forum question on how to remove local administrators from the sysadmin group. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1559584&SiteID=1
Be aware that this helps to keep honest people honest and prevent misuse by mitake, but it is only a speed-bump in case the machine administrator is truly malicious and determined to get to your data. As the machine administrator has full control over the machine and files stored there as well as any process running on it. I would strongly recommend a establishing a security policy so you can monitor and audit activity on both SQL Server as well as on the machine itself.
-Raul Garcia
SDE/T
SQL Server Engine
Drill down slow,Sql server