<div>
<div class="content wysiwyg-content">
Hi, we need to run our own webserver to hold a HR application. I set up IIS6 on win 2003 and put the box into the dmz which is configured on a Cisco ASA 5510. The firewall has been configured with security rules to allow incoming traffic on ports 80 and 443 and NAT to translate the public IP to the dmz IP address. I can access the website internally but not externally. We have a Cisco VPN server in the DMZ as well and it has a private IP as well as a public IP configured. When trying to do that on the windows server (it has two nics) one gateway will be removed. Obviously, I am missing something here - can anybody help?
</div>
</div>


Hi, we need to run our own webserver to hold a HR application. I set up IIS6 on win 2003 and put the box into the dmz which is configured on a Cisco ASA 5510. The firewall has been configured with security rules to allow incoming traffic on ports 80 and 443 and NAT to translate the public IP to the dmz IP address. I can access the website internally but not externally. We have a Cisco VPN server in the DMZ as well and it has a private IP as well as a public IP configured. When trying to do that on the windows server (it has two nics) one gateway will be removed. Obviously, I am missing something here - can anybody help?

webserver config in dmz

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).