Adding first server questions

Question

We are moving and are going to be adding a server (Quad 2.5 G5 w/ 2x500 HDs). We are currently have the internet connection coming in (static IP) to an AEBS running two printers and an AEX on the same network running the other. All the machines use the wireless network for internet access and printing. Email is via a hosted Exchange solution and another company hosts our web site. We have one spare machine that does limited file server work, but most folks have stuff on their hard drives.
I have read the manuals on OS X server and a couple of after market books and, since much of it is somewhat familiar, I am relatively confident about many of the software setup issues. However, I have gotten some conflicting advice about the physical configuration and hoped you guys could help.
We want to be able to use the server as a file server, with better access control than the sharing preference, have remote users connect with a VPN, use the wireless network for internet access and printing. We might want to host web sites via an intranet or be able to access them from outside, but don't want them to be associated with the domain name that is the real web site.
My first question is about the interface between the airport network and the server. I was originally told that the cable to the internet should go into one of the servers ports and the other should connect to an AEBS. I should set up the server to act as a firewall and serve up DCHP addresses. However, some of what I have read says that this is a bad idea--that the AEBS or something else should be the first in line and that the server should be connected to the LAN port of the AEBS. Which is best?
Other questions:
Should I use the server print services or just the bonjour through airport?
I don't need to set up the mail services, correct?
Anything else I should consider?
Thanks

Answer 1

Since no one else has chimed in yet I'll pipe up and suggest you consider another configuration: connect your internet modem to a standalone firewall/router. (You'll either need one with a built in switch, or you'll need to connect a standalone switch to it.) Then connect both your server and Airport to the switch. The Airport will be set to bridge your wireless network to the wired network.
This way you focus your server resources on real server stuff, while the router takes care of grunt work like NAT and DHCP. You also gain some isolation for your server compared to having it function as your firewall and gateway.
Just an alternative to think about.