Reporting Server Web Access

I would like to have access to the reporting web interface w/o having to VPN
or be local to the network. For testing, I configured my firewall so I could
access the server using a public IP / FQDN. The site is served up, I login
and can access all folders just fine. However, when I try to access a
report, I get a generic "The page cannot be dispalyed"

I suspect it is because I am accessing the server no using its host name.
Any suggestions? Thanks!

Sounds like you might not be a member of the SCDW Report users.

--
Regards,
Blake Mengotto
Email: mengotto@nospam.hotmail.com (remove the nospam if you want to email
me directly)
"MOM 2000/2005 - The ultimate solution for monitoring/managing your Windows
OS and applications."
http://www.momanswers.com - MOM solution center resource
http://www.microsoft.com/mom - MOM Application site
http://www.silect.com - MOM Health Reporter and MP Studio Express
http://www.excsoftware.com - MOM solution provider

That is what i thought, but it works just fine if I use the Internal IP. But
using the same credentials coming through a public, NAT'd IP, it fails. I
still see the Reporting Server "Interface" its just after I click on a
report, the internal frame returns "The page cannot be dispalyed"

When you installed SQL reporting services did you select SSL?

--
Regards,
Blake Mengotto
Email: mengotto@nospam.hotmail.com (remove the nospam if you want to email
me directly)
"MOM 2000/2005 - The ultimate solution for monitoring/managing your Windows
OS and applications."
http://www.momanswers.com - MOM solution center resource
http://www.microsoft.com/mom - MOM Application site
http://www.silect.com - MOM Health Reporter and MP Studio Express
http://www.excsoftware.com - MOM solution provider

If I create an LMHOSTS entry for the public IP to the server's netBIOS host
name, it works just fine.

Walter,

I had the same issue some time back and for me it was the webconfig
configuration of SQL reporting services pointing the hostname of the box. If
you look in your IIS logs you will probably find it is failing because it is
looking for the hostname of the machine. When you come in from the internet
it is working straight from the URL name, but when reports references
reportserver is looking at the host name. I had to configure a file called
webconfig to the URL and that fixed the issue.

Thank you very much for the responsse!!!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode test 33Switch to Hybrid Mode Switch to Threaded Mode

3 16th March 21:27 walter chomak External User Posts: 1	Reporting Server Web Access That is what i thought, but it works just fine if I use the Internal IP. But using the same credentials coming through a public, NAT'd IP, it fails. I still see the Reporting Server "Interface" its just after I click on a report, the internal frame returns "The page cannot be dispalyed"

5 16th March 21:27 walter chomak External User Posts: 1	Reporting Server Web Access no.

6 16th March 21:28 walter chomak External User Posts: 1	Reporting Server Web Access If I create an LMHOSTS entry for the public IP to the server's netBIOS host name, it works just fine.

8 31st March 01:10 walter chomak External User Posts: 1	Reporting Server Web Access Thank you very much for the responsse!!!