<div>
Hi Keith,<br />
<br />
We ended up opening the appropriate ports in the firewall to allow the webserver to communicate with the management server from the DMZ connection. &nbsp;Thanks for your prompt response.<br />
<br />
Mike
</div>


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

<div>
<div class="content wysiwyg-content">
Hello, we have a Windows Server 2003 R2 server already setup as a webserver in a DMZ which is working fine. &nbsp;However we recently installed an anti-virus client on it which needs to be able to &quot;phone home&quot; to a Management Server on the internal network. &nbsp;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. &nbsp;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 &quot;confuse&quot; the incoming traffic trying to get to the webserver on the DMZ side. &nbsp;We were wondering how we can setup the second NIC to allow the server to &quot;phone home&quot; to the internal server while preventing confusion of the web traffic coming in from the DMZ. &nbsp;Thanks for your help. &nbsp;Mike
</div>
</div>


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

Setting up webserver to work with DMZ and Internal network

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

The Internet Protocol (IP) is the principal communications protocol in the Internet protocol suite for relaying datagrams across network boundaries, organized in abstraction layers, traditionally called "Link," "Internet," "Transport" and "Application”. Its routing function enables internetworking, and essentially establishes the Internet. IP defines packet structures that encapsulate the data to be delivered. It also defines addressing methods that are used to label the datagram with source and destination information.

Internet Protocols

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).

Windows Server 2003

Microsoft Forefront, formerly known as Internet Security and Acceleration Server (ISA Server), is a network router, firewall, antivirus program, VPN server and web cache that runs on Windows servers. It includes identity management and protection systems, and discontinued systems for threat management and network protection, along with protection for Sharepoint and Exchange. The scope of discussions includes forward and reverse proxy, application and service publishing, virtual private networks (VPNs), outbound access rules, SSL certificates and network routing within either a single node or an highly-available array pairing.