How should I configure my SQL 2008 Reporting Services so that the Report Manager can be accessed outside the server. That is, from a different machine within the same network? Whenever I try to access the Report Manager from another machine, a prompt will appear requesting for username/password several times before a blank page is shown. Reporting Services Configuration Details: Service Account: Local System Execution Account: Tried using my own login details within the domain and tried without it Please let me know if you need any other details. I am running out of ideas on what I can possibly do, thanks!

Hi, You need to add report server URL as a truested site on other box. You may also need to also set Automatic Logon which is last in list in internet options(Tools->Options->Security->Custom Level) -Chintak

Thanks for your reply. I have added the http://<servername> to the Trusted site list, and made sure that the Security settings is set to Automatic Logon, but the same problem occurs. Any other settings that I can try?

Hi, Do yoy have firewall running where SQL SERVER Reporting service is running? If so, you need to ensure that port 80 not blcoked for incoming requests as shown here. http://msdn.microsoft.com/en-us/library/bb934283.aspx Hope this helps. -Chintak

Also, make sure that the user who is logging onto the report server is added to report manager and given the appropriate permissions. Even this could be one of the reason why the user is unable to login to report manager.Phani Note: Please mark the post as answered if it answers your question.

The user has been added to the security settings within the report manager. There is no Windows Firewall running, as the Windows Firewall service is actually disabled. However, there is a Symantec Endpoint Protection running on the server, and I am yet to find a way to disable the Network Threat Configuration (it doesn't allow me to select it). I guess this will lead us into a separate issue now!

To disable Network Threat Protection you can uninstall Symantec Entperprose Protection, then reinstall it. During reinstallation, select "Only Antivirus and Antispyware". I have used this installation method for iis and sql servers and have had no problems.

This is the EXACT problem that I have described in my earlier question asked about an hour or so ago. I am being told by my support vendor that it is a Microsoft acknowledged bug but have had no responses to my thread either way. I/we thought it was related to R2 though so I am unsure this is an exact relationship. Are you on R2?