November 25, 2005 at 6:27 am
I am connecting to a SQL2K box on the network using trusted connections.
The ASP.NET pages are on my local box running IIS6.
When I run the pages everything works fine.
When anyone else tries to hit page that does database access they get "Cannot logon with user NULL NT\Authority error."
It clearly does pass my user credentials from my box, otherwise I wouldn't be able to get any data access.
All other testers have identical rights to the SQL Server box.
The web application is set to use Windows authentication, anonymous access is denied.
web.config allows impersonation.
I've no idea what to investigate next and should be grateful for any help.
November 27, 2005 at 2:54 pm
This is approximately the same message that my users were getting when trying to connect without logging into the domain. That fix follows:
When you attempt to connect to the SQL development server from your non-domain connection you will receive the following error message:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection |
You can fix this in XP Pro and Server 2003 (not Home Edition or Server 2000) machines by doing the following:
Start | Control Panel | User Accounts | Advanced | Manage Passwords | Add
And then load the Server Name and a Windows Authenticated username and password that will give you authentication to the server. From that point on you have trusted credentials to access the server without actually logging into the domain.
On the server side I had to add their domain user ID into one or more of the following groups:
Descriptions of the available groups follow:
1. SQL Server Integration Services
2. SQL Server FullText Search
3. SQL Server Analysis Services
4. SQL Server Active Directory Helper
5. SQL Server and SQL Server FullText Search
6. SQL Server Notification Services
7. SQL Server Reporting Services (web)
8. SQL Server Reporting Services (non-web)
9. SQL Server Agent
10. SQL Server Browser
This last step was not immediately obvious since I tested from a non-domain client with my domain account which was an administrator on the host. Once this was done it was smooth sailing.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply