I have noticed one other problem as well, running on SQLTEST02.

After switching Reporting Services to run on SQLTest02 and connecting to it using one of my DNS entries:

- sqltestrs/reports

- iristestrs/reports

- scatsrs/reports

I get the Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

If I logon via sqltest02/reports I can run the report and it authenticates using kerberos.

I can then go back to using one of:

- sqltestrs/reports

- iristestrs/reports

- scatsrs/reports

and the report will run successfully, even after closing my web browser and launching a new web browser session?

It would appear I get a ticket for HTTP/sqltest02.forthports.net - which would possible explain why it works, but why is it not working for my dns entries?

I had to configue Reporting Services to RSWebApplication.config file <ReportServerUrl> to:

<UI>

<ReportServerUrl>http://sqltest02/ReportServer</ReportServerUrl&gt;

<ReportServerVirtualDirectory></ReportServerVirtualDirectory>

<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>

</UI>

as the reporting services website is not the default website. (I also setup the host headers)

Is the config file part of the reason why it only generates a ticket for sqltest02 and not my dns references, that I have created http SPN's for?