Newbie and authentication

Last Post 29 Oct 2004 01:53 PM by acarheden. 4 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Janetb99
New Member
New Member

--
14 Oct 2004 10:02 AM
Have Server2003, IIS6 with multiple websites, sql2000, and just installed reporting services. After making my first simple report with graph to see how this works (XP pro), I published to the server. But, I was the only one able to see it using the server name. So, I changed the permissions on the reportServer and reports under IIS Default website to allow IUSR_serverName to read/execute and enabled anonymous access with IUSR_serverName.

Now, if I want to deploy update to report to web I have to take off the new IUSR permissions and then put them back. And, only folks within the company could get to the report - dns is done at the firewall.

So, I made a virtual directory under IIS within the web called Reports, and made sure the permissions on the virtual directory were set to read/execute.

Now, if I use a dial-up and a url similar to below, I'm told the user doesn't have permissions to view the page.

http://www.mydomainname.com/reports...and=render

I've probably done a thousand things wrong - anybody willing to enlighten me?

Thanks so much.

Janetb99
New Member
New Member

--
15 Oct 2004 03:52 AM
I did find this, but had questions:
1. Do I remove the virtual directory under IIS?
2. The error message I receive when deploying to the server and after giving the IUSR account read/execute permissions under reports/reportServer - is referring to deployment or telling me that it deployed the new report but that my settings don't give the correct permission for the account to access the report?
3. I have more than one website. Does the item below mean that I have to specify one of the domain names and use it for all?

Here's what I found?


To access a report server on the Internet, you must add a ReportServerExternalURL configuration setting that specifies the fully qualified domain name of the report server. The external client uses this value to access a report server. In this scenario, the browser that is hosting Report Manager must send a fully qualified domain name when making requests on behalf of Report Manager to the report server.

The following example illustrates the syntax for ReportServerExternalURL:

<ReportServerExternalURL>reports.adventure-works.com</ReportServerExternalURL>


c:under ReportManager
config file:

<Configuration>
<UI>
<ReportServerUrl>http://WAHOO/ReportServer</Repor...verUrl>
................does the url go here? reports.mydomainname.ext
</UI>
etc......
</Configuration>
Janetb99
New Member
New Member

--
29 Oct 2004 05:28 AM
Bill,
Thanks so much for the reply, but that won't work. If you use split-brain dns, as many do, your ip scheme behind your firewall is different that the ip scheme seen by the world. This provides added protection.

So, if you use an ip address rather than a domain name for your url, users will never be able to find your server when trying to locate it out on the internet.

Janet
acarheden
New Member
New Member

--
29 Oct 2004 01:53 PM
Janet,

Not to promote another site, but did you see this link. I came across another posting you made while looking up some stuff related to your question. I'm still looking for a better answer for you, but please let us know here if the link above is helpful.
Janetb99
New Member
New Member

--
10 Nov 2004 10:25 AM
Well, Bill, it currently creates a problem for us because of the split-brain, split-ip dns. We really need to be able to use the domainName and NOT the ip address.

To date:

Have split-brain dns (Server2003
with AD) 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

Also, since reporting services is on same box as web services, tried replacing config file with:
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>


Same errors.

Any ideas?

Janet

You are not authorized to post a reply.

Acceptable Use Policy