I'm unable to connect to http://servername/reports[server] using IE 8 or 9 with default configuration on client systems, but can connect to those same URLs using IE 8 on the SQL Server/SSRS system. The result on the clients is always "Internet Explorer cannot display the web page", like the response you get when a web site is unavailable. Business Intelligence Development Studio/SSMS on the client systems does connect to the SQL Server/SSRS system. It seems that the HTTP request gets to the SSRS system, but HTTP.sys does not respond. Tried collecting an event trace from HTTP.sys on the SSRS system. It does show a trace using IE 8 from the SSRS system itself, but nothing from the client systems. Duplicated the test to make sure. No errors in httperr1.log. Tried using "all unassigned" for the report service and report manager. No change. Particulars: SBS2008 Premium (single domain) with SQL Server 2008 on second server. All updates applied. No odd events on any systems. Recent install of SSRS. Using default configuration, without SharePoint integration. SSRS using Windows authentication. No SSL. Domain user account for services. Site settings showing correct security settings. ISA 2006 is involved, but nothing I have tried makes any difference; not enabling a "allow everything" rule, adding the SSRS server to the proxy server bypass list in IE, setting IE to not use the proxy server, or adding http://servername to the Local Intranet. On the SSRS system I can see two to four port 80 requests coming from the client with Network Monitor 3.4 before IE gives up. So the problem does not seem to be ISA. This is the only thing that I know of that does not work on these systems and in this domain. Any suggestions on what to try? Thanks. David

Hi David, Thanks for your question, from your statement, you mentioned that you could not connect Report Server or Report Manager on client system, but you could connect to Report Server or Report Manager on SQL Server/SSRS system, based on these information, we could indicate that Reporting Services has no issue as you could visit it correctly on SQL Server/SSRS system. Since your SSRS using Windows authentication, every user should be permited to visit Report Server or Report Manager. You can define system-level role assignments to grant access to global tasks and permissions that apply to a report server site as a whole. Each user who requires access to a report server should have a system-level role assignment. You can use the predefined roles that Report Manager provides to create the assignments. After that you have to set permissions for accessing report server content, including reports, models, folders, shared data sources, and resources. For the detail steps for configuring site-wide permissions, please see: http://msdn.microsoft.com/en-us/library/aa337385(v=SQL.105).aspx For the detail steps for setting permissions for accessing report server content, including reports, models, folders, shared data sources, and resources, please see: http://msdn.microsoft.com/en-us/library/aa337471(v=SQL.105).aspx Thanks, Challen Fu Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Challen, Thank you for responding. I am making my way through the documentation, but had already seen the site security settings page on the Report Manager web site, and had added a group for SSRS users (including my domain account), and another for SSRS administrators (including domain administrators). I also specifically added my own domain account with full SSRS permissions. I cannot connect from the domain client systems with either my account or the domain administrator account, but I can connect from the SSRS server itself as the domain administrator. The question is if there are low level means of tracing what happens when a request comes in to the SSRS system. If I cannot even see client activity on a HTTP.sys event trace, but can see client packets coming in with Network Monitor, what else can I do? The request is apparently not even making it to the part of SSRS that handles HTTP requests and performs authorization. It is not even making through HTTP.sys, at least for the clients. It works fine only from the SSRS server. So the SSRS web sites are correctly registered. Has anyone using SSRS encountered this problem of client "no", server "yes"? How would you trace HTTP requests to HTTP.sys? Is there something beyond ETW tracing? Is there some flag that can be set to see more? Is there some step-by-step procedure to follow to resolve this? I know that you can trace the SSRS HTTP module but the request is not making it that far. I must be missing something very simple, and will be embarrassed when it is found. This should just work. Thanks.David

I'll answer this one. I installed new components of SQL Server today, including SSIS. There were no other configuration changes made. I don't know when SSRS from a client started working, even in IE 9, but it did. Case closed.David