jscrime
asked on
SQL Server Reporting Services, DMZ, Public Reports
I am looking for the best/safest way to perform the following:
We have SQL Server 2005 with SQL Reporting Services running on a Windows 2003 Server box behind our firewall. We also have a Web Server running in a DMZ behind the firewall.
We are looking to use Visual Studio .Net 2005 and the integrated SQL Report Viewer Control to display Reporting Services Reports on Web Sites in the DMZ.
1) What ports would have to be opened in the DMZ to communicate with SQL Server and SQL Reporting Services
2) Where/How is the best way to control authentication from the ASP.Net Report Viewer Control to the Reporting Services Report ( From DMZ to private network)
Any help in getting this scenario running without compromising security would be appreciated!
Thanks
We have SQL Server 2005 with SQL Reporting Services running on a Windows 2003 Server box behind our firewall. We also have a Web Server running in a DMZ behind the firewall.
We are looking to use Visual Studio .Net 2005 and the integrated SQL Report Viewer Control to display Reporting Services Reports on Web Sites in the DMZ.
1) What ports would have to be opened in the DMZ to communicate with SQL Server and SQL Reporting Services
2) Where/How is the best way to control authentication from the ASP.Net Report Viewer Control to the Reporting Services Report ( From DMZ to private network)
Any help in getting this scenario running without compromising security would be appreciated!
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
and better use VPN to encapsulate all traffic between web server and SQL server. otherwise, 1) several ports need to be exposed and redirected 2) firewall performance considerations.