Multihomed server on LAN an DMZ

We have a new server that is going to replace our existing web server,
we also want to use this server as an application server to run an
Adobe enterprise PDF program. Would it be best to make this a
multihomed server and have one nic on the LAN the and other on the
DMZ? This system is a HP ML370 running Windows 2003 server and it is
a member server. If multihomed is best, how is the best way to keep
all DMZ traffic from getting on the LAN? If multihomed is not the
best way to go could someone please suggest a different way.

Thanks

In news(E-Mail Removed),
Jeff <(E-Mail Removed)> typed:
> We have a new server that is going to replace our existing web server,
> we also want to use this server as an application server to run an
> Adobe enterprise PDF program. Would it be best to make this a
> multihomed server and have one nic on the LAN the and other on the
> DMZ? This system is a HP ML370 running Windows 2003 server and it is
> a member server. If multihomed is best, how is the best way to keep
> all DMZ traffic from getting on the LAN? If multihomed is not the
> best way to go could someone please suggest a different way.
>
> Thanks

Why would you want two NICs? I'd just stick it in the DMZ with one NIC, and
open up LAN-->DMZ ports as needed (but not vice-versa).

"Jeff" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> a member server. If multihomed is best, how is the best way to keep
> all DMZ traffic from getting on the LAN?

It won't as long as the machine isn't configured to operate as a router.
Just because a machine has two nics does not mean it will route between the
two segments it is joined to. It has to be "configed" to do that.

However you can "publish" the webserver from right where it is sitting by
using the Firewall and you would be avoiding the whole idea all-together.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com