Reports inaccessible from the Internet

Last Post 03 Nov 2004 05:03 AM by Janetb99. 25 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Page 2 of 2 << < 12
Author Messages
Janetb99
New Member
New Member

--
03 Nov 2004 06:41 AM
Thanks expert - I agree. I've made so many changes trying to get it to work, I've probably hosed it beyond repair. But, I thought you couldn't uninstall Reporting Services?

If it appears that I can uninstall, got any steps and tips so that I don't repeat any mistakes?

I really want to use this but am frustrated and now have five folks that have emailed me with the same problem awaiting the outcome.

Thanks so much for taking the time.
Janetb99
New Member
New Member

--
03 Nov 2004 11:49 AM
Okay, I've uninstalled, reinstalled and installed rs service pack 1.

I created and deployed one report.
I added the following to the config file without changing any IIS or RS users, roles or settings.
<ReportServerExternalurl>http://www.mtn.ncahec.org/ReportSer...nalurl>

I get page not found. What would you recommend before I start messing things up again?

Janet
jlimmer
New Member
New Member

--
03 Nov 2004 12:03 PM
First, your case (<ReportServerExternalurl> is wrong. It should be <ReportServerExternalUrl>.

That being said, are you getting "Page not found" via your intranet? If so, do you have a DNS 'A' record set up for "www.mtn.ncahec.org/ReportServer" on your internal DNS server?

Can you browse to http://www.mtn.ncahec.org either/both from your LAN and from the Internet? (I can get to it okay. ) This will determine if you have the internal DNS set up to get to a domain known on the outside of your network.

Is your report server behind a firewall or generally accessible from the Internet?


Janetb99
New Member
New Member

--
03 Nov 2004 12:11 PM
Those pesky cases.... sorry.... it's fixed. Faces earned and appreciated.

Our dns is a split-brain with the external ips different than internal and they are natted at the firewall. External folks can get to the regular ole websites (intranet and internet) fine.

Nobody at this point can get to anything unless they are logged into the network using the serverName/reportserver method. Right now I've only tested the new install behind our firewall. If I can get that going with the domain name, I can then test outside the firewall.

***That being said, are you getting "Page not found" via your intranet? If so, do you have a DNS 'A' record set up for "www.mtn.ncahec.org/ReportServer" on your internal DNS server?***

I have an A record for the www.mtn.ncahec.org - do I need a separate one for the report server? Or, do I need virtual directories under the www.mtn.ncahec.org IIS site? We have three very small websites - I'd like to be able to use for all three since I'm basically what you'd call the web/database/development staff (of one).

You're very patient and very wonderful - please keep responding.



jlimmer
New Member
New Member

--
03 Nov 2004 12:38 PM
I feel like we're not communicating on this one. Let me try a high level approach. I apologize if my explanation below goes overboard unnecessarily but it just seems to me that you are perhaps getting internal and external DNS functions confused.

Public websites are set up on some domain registration server who sets up an 'A' record that points people outside your network to your website. That's apparently www.mtn.ncahec.org in your case. That would mean that your RSWebApplication.config file should be using the <ReportServerExternalUrl>http://www.mtn.ncahec.org/ReportSer...nalUrl> entry.

As long as security is set appropriately (either using anonymous <though not recommended> access or some form of authentication [Windows authentication, for example]), this should let users get to your report service (which would normally be set up by default as http://www.mtn.ncahec.org/reports)." target="_blank" rel="nofollow">http://www.mtn.ncahec.org/reports).

Virtually all business networks also have an internal DNS server handling requests from internal network clients. Assuming that your internal network is NOT named the same as your outside domain, you would have a DNS zone for your internal domain.

To get your internal users to access your report server as an intranet site, you need to add a new primary zone in your internal DNS server using the name 'mtn.ncahec.org'. You then need to add an 'A' record for 'www' that uses the internal IP address of your web server.

That will let your internal users browse to the report server using the same domain name as your outside users (http://www.mtn.ncahec.org/reports)." target="_blank" rel="nofollow">http://www.mtn.ncahec.org/reports). This works because the <ReportServerExternalUrl> entry will be valid internally because of the new entries you will have made on your internal DNS server.
Janetb99
New Member
New Member

--
04 Nov 2004 10:44 AM
Got DNS (I think) - set up a DNS server. Have split-brain dns natted at the firewall with 5 domains - one internal only and dynamic; all others static for basically websites and email pointers. Websites, email, sql, asp pages are working fine - EXCEPT REPORTING SERVICES!!!

I have uninstalled, reinstalled, added IUSR_MachineName to users and role assignment as browse in RS. Gave IUSR_MachineName read permissions to folder and have the following to report:

With <ReportServerExternalUrl>http://domainName/ReportServer</...nalUrl>" target="_blank" rel="nofollow">http://domainName/ReportServer</...nalUrl>" target="_blank" rel="nofollow">http://domainName/ReportServer</...nalUrl> not added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set to no anonymous and winAuth on: Security options and reports display appropriately. Not viewable using interal ip address. Viewable from outside the firewall using external ip address only after login prompt.

With <ReportServerExternalUrl>http://domainName/ReportServer</...nalUrl>" target="_blank" rel="nofollow">http://domainName/ReportServer</...nalUrl>" target="_blank" rel="nofollow">http://domainName/ReportServer</...nalUrl> added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set to anonymous and winAuth on:
Using Internal IP: Login, then Folder Listing, Security options do not display and reports give page not found. Report server - report viewable
Using ServerName: Login, Folder Listing, Security options do not display and reports give page not found. Report server - report viewable.
Using External IP outside Firewall: Login, Folder Listing, Security options do not display and reports give page not found under Reports. Report server - report viewable.
Using domain name: Reports - page not found, ReportServer - page not found.

With <ReportServerExternalUrl>http://domainName/ReportServer</...nalUrl>" target="_blank" rel="nofollow">http://domainName/ReportServer</...nalUrl>" target="_blank" rel="nofollow">http://domainName/ReportServer</...nalUrl> added.
Within IIS Reports set to no anonymous and winAuthen on and ReportServer set to anonymous and winAuth on AND virtual directories added under website AND home.aspx added and moved to top under documents for virtual directory:
Using Internal IP: Folder Listing (no login), Security options do not display and reports give 403.8. Report server - report viewable
Using ServerName: Folder Listing (no login), Security options do not display and reports give 403.8. Report server - report viewable.
Using External IP outside Firewall: Login, Folder Listing, Security options do not display and reports give page 403.8. Report server - report viewable.
Using domain name url: Reports - 403.8; ReportServer - 403.8

Next?

Janet







You are not authorized to post a reply.
Page 2 of 2 << < 12


Acceptable Use Policy