What I want to do is this 1. Use the Report Viewer from a Front End Web Server 2. Point back to a Report Server to get various reports that all can be public 3. Allow anonymous access for public reports 4. Configure logins for private reports The biggest issue I have seems to stem from how Reporting Services receives the Credentials from the web server. I can get the report viewer to seemingly load the report, but no charts are displayed. I have enabled a specific account to allow for graphics and such but that does not work either. I can hardly believe that Microsoft made it this hard to display a report out on the www. Was the intent to install reporting services on the web server? If so I can get things to work just fine. The issue is when the report server is in the background being called from a web application. If I run the project from local configured for NTLM access everything works fine in Visual Studio. It bonks once the project is promoted to a web server. I have read the anonymous access threads and just do not believe that such a brute force and highly exposed route is required. I can make this work just by installing Reporting Services on the web server that I need to deliver the report, use the Report viewer and then point back to the Report Server. It just does not work when Reporting Services is not on the web server. Any Ideas? Thanks Rob

Hi, Arer 6your WFEs SharePoint? -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.