June 21, 2006 at 8:53 am
If I try to run a report using trusted security from my browser the report fails with the Login failed for user (null). If I use SQL authentication then it works ok.
If I remote connect onto the server hosting reporting services then it works ok using trusted security.
To explain better:
Laptop running IE, browsing to ServerA/reports trying to connect to ServerDB fails.
ServerA running IE, browsing to ServerA/reports trying to connect to ServerDB succeeds.
I guess it is an ASP.NET localhost thing, but I've installed the defaults so I would have thought by default SSRS should be able to use trusted security to another DB on the same domain.
Any ideas?
June 23, 2006 at 7:00 am
This is a problem with the way the network credentials are passed on from the client to the server on a windows network. What is probably happening here is you have Reporting Services installed on one box and it is trying to access SQL server on another box. You are authenticated on your client PC using IE. Then you connect to Reporting Services on the server and your authentication token is passed to that server. Reporting Services tries to get the data but the network does not allow this second hop of your authentication token so you the above error.
The solution is to implement kerberos authentication between the two boxes.
June 23, 2006 at 7:21 am
Thanks for the reply, I had just figured out that if the DB was on the same server as the Report Server then Trusted connectivity worked, so I guessed it was a 2-hop problem.
I'll chat with our Infrastructure guys about how to implement kerberos
thanks
Neil.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply