Hi,I'm trying to deploy Reporting Services on an Internet-facing web server using a custom security extension (forms authentication). We will be putting Report Manager on the Web Server outside of the firewall, and Report Server on another machine inside the firewall. When testing the solution in a development environment with Report Manager and Report Server on the same box, the solution works fine.When testing it using the Internet-facing environment described above, it almost works but there seems to be an issue with the authentication cookie that is generated. Here's what happens:1. User enters credentials on UILogon.aspx and submits form.2. In the code-behind, LogonUser() is called through a web service proxy and the authentication cookie is returned successfully. The code used here to set the cookie is the same code used in the Forms Authentication sample that ships with RS2005.3. The user is redirected to Folder.aspx, and the request hangs for a while, and eventually kicks you back out to UILogon.aspx, as if it lost the authentication cookie. When doing a trace on the HTTP header, the cookie is still there.Is there anything special I need to do to make the Report Server "see" the cookie when I have Report Manager and Report Server on different machines?Any help would be much appreciated!Mike

Hi Mike, Did you manage to get a solution to your problem? I am having the same problem as your. I have manage to have a work around but it was a bit strange. If I use http://localhost/reportserver (it work - no loop back to login page). If I use http://IP Address/reportserver (it work - no loop back to login page). Not working If I use http://Machine Name/reportserver (NOT WORK - loop back to login page). Dat