Showing posts with label internal. Show all posts
Showing posts with label internal. Show all posts

Wednesday, March 21, 2012

DNS, Internet and Reporting Services

Seem to not be able to get set up right. 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</ReportServerExternalUrl> 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</ReportServerExternalUrl> 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</ReportServerExternalUrl> 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?
JanetHello Janet,
If the Report Manager and Report Server are on the same machine then remove
the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
in the config file - and replace with this:
<UI>
<ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
</UI>
Peter Blackburn
Author: Hitchhiker's Guide to SQL Server 2000 Reporting Services
http://www.sqlreportingservices.net
"janetb" <janetb@.discussions.microsoft.com> wrote in message
news:EB70D3CE-FA1F-4445-9B52-48F0FCA11096@.microsoft.com...
> Seem to not be able to get set up right. 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</ReportServerExternalUrl>
> 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</ReportServerExternalUrl>
> 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</ReportServerExternalUrl>
> 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|||Peter,
Thanks so much for replying. I made the change, but unfortunately there was
no change. When I try to use the url with the domain name instead of the ip
address or machineName, I still get the 403.8 dns error. I even tried
removing the virtual directories for reports and reports server from the
website - no change.
Any other ideas?
Thanks,
Janet
"Peter Blackburn (www.sqlreportingservice" wrote:
> Hello Janet,
> If the Report Manager and Report Server are on the same machine then remove
> the <ReportServerExternalUrl> and the <ReportServerUrl> from the <UI> node
> in the config file - and replace with this:
> <UI>
> <ReportServerVirtualDirectory>/ReportServer</ReportServerVirtualDirectory>
> </UI>
> Peter Blackburn
> Author: Hitchhiker's Guide to SQL Server 2000 Reporting Services
> http://www.sqlreportingservices.net
>
> "janetb" <janetb@.discussions.microsoft.com> wrote in message
> news:EB70D3CE-FA1F-4445-9B52-48F0FCA11096@.microsoft.com...
> > Seem to not be able to get set up right. 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</ReportServerExternalUrl>
> > 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</ReportServerExternalUrl>
> > 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</ReportServerExternalUrl>
> > 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
>
>

DMZ Web Server and Internal SQL Server

I have a .net web application that is running on a w2k server located in our
DMZ it has a private address. The SQL server is also running on a w2k server
but it is located in our private network. I have opened port 1433 on the
firewall from the DMZ to Lan and from Lan to DMZ. Since neither server knows
the other excist I have added an entry in the local host file of the
webserver in the DMZ that points to the internal SQL server. Does an entry
also need to be placed in the host file of the SQL server? Also what would
be the proper connection string in the web.config to link these two servers
together? And would anything need to be done on the SQL server?
Thanks
You may need to specify the IP address of the firewall and 1433 to allow
the connection to succeed, since the client won't know how to resolve the
netbios or host name of the server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
sql

DMZ Web Server and Internal SQL Server

I have a .net web application that is running on a w2k server located in our
DMZ it has a private address. The SQL server is also running on a w2k server
but it is located in our private network. I have opened port 1433 on the
firewall from the DMZ to Lan and from Lan to DMZ. Since neither server knows
the other excist I have added an entry in the local host file of the
webserver in the DMZ that points to the internal SQL server. Does an entry
also need to be placed in the host file of the SQL server? Also what would
be the proper connection string in the web.config to link these two servers
together? And would anything need to be done on the SQL server?
ThanksYou may need to specify the IP address of the firewall and 1433 to allow
the connection to succeed, since the client won't know how to resolve the
netbios or host name of the server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.