Setup I did: * Installed Reporting Services sql 2008 in "files-only" mode This box does NOT have IIS installed. * Configured report server to use port 80 and virtual directory "ReportServer". (Open inbound port 80 in firewall on server.) Locally, http://<server>:80/Reports and http://<server>:80/ReportsManager work fine Issue: From an external box, http://<server>:80/Reports is not accessible. It returns "Internet Explorer cannot display the webpage" What am I missing? (Am I supposed to setup a "URL Reservation" per http://technet.microsoft.com/enus/library/bb630447.aspx. I don't know.) TIA, Barkingdog

I found the answer. I setup the port 80 inbound rules on the server for "Domain, private" only and the Reports were inaccessible. When I set port 80 for "public" access it works. I guess I don't understand the difference bewteen the two settings. The former seems more secure than the latter (Public). Barkingdog

Hi, I have a similar issue. Both /Reports and /ReportServer urls work fine on the server itself, using the servername and its ip-address. Remotely however, url's with the servername don't work, only url's with the ip-address work. I can ping the servername, nslookup looks fine, but using the servername in the url gives "Internet Explorer cannot display the webpage". It is a clean Windows Server 2008 R2 install, with only a SQL database and Reporting Services. IIS and others have not (yet) been installed. The firewall is set to allow port 80 for all profiles. I also tried to configure everything to use port 90, but no luck. I just checked the servers again and it was working. Until I rebooted the remote server (didn't touch the reporting server). After the reboot ping and nslookup still look fine and url's with ip work, but with servername fail again. I have no idea why it somehow started working or why it is now failing again. Can anyone tell me what I'm missing here? Thanks in advance. Jeroen