Question Locked

DMZ configuration question

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a customer that shares an internal network with a completely different customer. Customer A and customer B are on 192.168.2.x network and both use the same application for their daily business. Customer B needs to setup a local web server for a separate application that only they use. Customer A does not want to open up their network to web traffic at all. Customer B is going to bring in a separate internet connection with a static IP for web server hosting. Customer B runs a database program that is going to run on the webserver. Customer B has to have constant access to the database/web server to input data. Any configuration recommendations for this scenario?

Thanks

2 replies

by cg it

the question I would have is does the web server actually have to be on the internet? If not, you don't have to have a DMZ. you can control user access on the LAN where only those users from company B can gain access and still have the web server on the LAN as long as the web server isn't exposed to the Internet.

also why a web server to run an application that has a database?

If the web server must be exposed to the Internet, and you have the $$, I'd use ISA server in a cluster with a perimeter and network firewall with the web server in between and the database on a different server behind the network firewall ISA server.

publish the web server and have AD intergration for user authentication. This way you can control who can gain access to what via AD rather than try with IIS admin.

This discussion is closed to new replies.