Help! How to properly configure a win2k3 web server (network connection, DHCP setting...)

we are setting up a new server on our network to host our website, database(SQL) and it's also the application server. trying to get help on setting up the whole office network...

Our T1 line came with a Cisco 1721 router, DHCP is not setup on this router.

here is a list of our equipment

1 x Dell 2950 server has 2 x Gigabit NICs.
1 x Cisco 1721 Router (NO DHCP)
1 x Dell switch
a few work stations
a few VOIP adapters
a few network printers
T1 Line

Server has AD deployed and DCpromo'd, DNS is setup correctly.

Now my question is, can someone suggest how they should be connected?

A* T1 -> Router->Switch->Server NIC_0,workstations,printers...etc , disable NIC_1

B* T1 -> Router -> Server NIC_0 , Server NIC_1 -> Switch -> workstations, printers..etc

C* T1 -> Router -> Switch -> Both NICs on server, workstations, printers..etc

the server will see a lot of incoming traffic because it's running as a web server too, so we do not want the internal workstations take up too much resources, but we do use a lot of bandwidth intensive work.

A seems like a bad idea , eh?

if we go with B, obviously all the outbound traffic must past through the server and will take up some bandwidth on NIC_0, this will reduce the available resources on this NIC and slow down the incoming web requests, am i correct?

if we go with C, i can assign two different IPs on both NIC, and the workstations are connected directly to the router, so it won't consume all the resources on the server.

any suggestions?

Who is Participating?
exhaustConnect With a Mentor Commented:
C is definitely the way to go.  You have 2 server NICs at your disposal, use them both for failover and load-balancing purposes. Just team them up using driver that Dell provided.

Obviously you'll have to enable port forwarding to port 80 on the router for it to pass these socket request to the server's ip address.  

As you already mentioned B will bog down the server with unnecessary traffic,  let the networking hardware take care of the network trafficking. HW is hundred times more efficient in doing it's job than SW based routing. That sure is a potential bottleneck.

In summary, attach all server, workstation , printers , other hosts etc... to the switch. This will all local traffic , well, local.  And only traffic that router will handle is external routing.
mike2016Author Commented:

we have a problem,though.  the Cisco router is not configurable by myself, because it's provided by the ISP, if we make any changes we must tell them to do it. we don't have the user id and password for it.

And I just ordered a Cisco PIX 506 firewall,  can I do port forwarding on the firewall instead on the router?

Should I setup the network like,   T1 Router -> Firewall -> Switch (all devices connected to it)  ?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.