Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Setting up webserver to work with DMZ and Internal network

Posted on 2012-03-22
3
Medium Priority
?
627 Views
Last Modified: 2012-03-23
Hello, we have a Windows Server 2003 R2 server already setup as a webserver in a DMZ which is working fine.  However we recently installed an anti-virus client on it which needs to be able to "phone home" to a Management Server on the internal network.  We have opened ports specified by the vendor which would supposedly allow it to see the Management Server from within the DMZ, but it still cannot.  The web server has a 2nd NIC on it which we use to connect it to the internal network when needed, but we cannot leave it connected all the time, as this will "confuse" the incoming traffic trying to get to the webserver on the DMZ side.  We were wondering how we can setup the second NIC to allow the server to "phone home" to the internal server while preventing confusion of the web traffic coming in from the DMZ.  Thanks for your help.  Mike
0
Comment
Question by:miket71
  • 2
3 Comments
 
LVL 51

Accepted Solution

by:
Keith Alabaster earned 2000 total points
ID: 37756030
You don't - you REALLY don't want to do this. You fix the issue that is currently precluding the DMZ server from talking over the internal firewall to the internal server instead.

If you connect another nic directly to the internal network then anyone who gains access to the dmz box has access to your internal network. If the DMZ box DOES get infected, which will be quicker, the main server manages to disenfect the DMZ box or the trojan/virus/whatever activates and is onto your network? Not a risk I would put my name to or expose my organisation to.

Most of the main players in the AV field (Sophos for example) now have two ways to deploy their updates. The first being through an internal server - much as you have by the sound of it. The second being through an on-line portal - and it is this second route that you point devices such as the DMZ servers. Your internal server console should still be able to 'manage' the DMZ box to check status etc but it all goes via the firewall - not a direct connection that bypasses your security perimeter.

Keith
0
 

Author Comment

by:miket71
ID: 37756874
Hi Keith,

We ended up opening the appropriate ports in the firewall to allow the webserver to communicate with the management server from the DMZ connection.  Thanks for your prompt response.

Mike
0
 
LVL 51

Expert Comment

by:Keith Alabaster
ID: 37757018
More than welcome. :)
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This article will show how Aten was able to supply easy management and control for Artear's video walls and wide range display configurations of their newsroom.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

971 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question