January 29, 2008 at 5:52 am
I've a new instance of SQL 2005 x64 running on Windows 2003 R2. The SQL instance is intended as back-end support for Sharepoint WSS 3.0 Extranet traffic. The SQL instance is behind our firewall in one domain while the WSS Extranet is in a DMZ within another domain. I've successfully done this before with SQL 2000 and WSS 2.x.
The problem I'm having currently is that when I try to add our Extranet support login to the SQL Instance I get the following error:
Create failed for Login 'domain\login-name'
Windows NT user or group 'domain\login-name' not found. Check the name again. (Microsoft SQL Server, Error: 15401)
o The SQL Server can ping the DMZ Domain Controller (and can be pinged from the DMZ Domain Controller.
o I can add the target DMZ windows account to the SQL Server
o I can add logins from other (and local) domains
o The collation sequence on the SQL Instance is: SQL_Latin1_General_CP1_CI_AS
o I've checked for duplicates in the master..syslogins (clean)
I've looked around on the web and found others having this issue but no definitive answer.
Any help would be gretly appreciated!
Glenn
January 29, 2008 at 8:36 am
Finally an answer!!!
Here's my solution:
o On the SQL Server - add the cross-domain account as a local administrator
o Log on to the SQL Server using the new cross-domain account
o Add the SQL Login for the cross-domain (using the SQL GUI, CREATE LOGIN, or sp_grantlogin) - should now create without the 15401 error (or any other error).
o Log off and back on to the server (using your 'normal' local admin account and remove the cross-domain account.
Hope this helps someone else
Glenn
August 30, 2010 at 4:20 pm
Glenn Owens (1/29/2008)
Finally an answer!!!Here's my solution:
o On the SQL Server - add the cross-domain account as a local administrator
o Log on to the SQL Server using the new cross-domain account
o Add the SQL Login for the cross-domain (using the SQL GUI, CREATE LOGIN, or sp_grantlogin) - should now create without the 15401 error (or any other error).
o Log off and back on to the server (using your 'normal' local admin account and remove the cross-domain account.
Hope this helps someone else
Glenn
The above worked for me. Any ideas on a cause and long term fix??
Thanks,
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply