I've recently been assigned to manage a network at work. There are two labs (over 40 clients in total) connected to one Windows 2008 r2 server. Roles installed are as follows:
File Services (for sharing)
Network Policy and Access Services (RRAS)
The server is an HP Proliant ML110 (which comes with two network interfaces).
AD DS is working fine, clients can join the network, and login with AD User credentials. DHCP is able to lease IP addresses fine. File Services is also okay, as network drives can be accessed by accounts.
The only real and major problem is that the clients can't get Internet connection from the server. Clients are supposed to acquire their Internet by getting it from the Win2k8-R2 server. This is really weird as the server itself has Internet connection. Also, on our older server, we were able to get this setup running until one of its NICs gave up, I believe. Then we shifted to the current HP.
While searching around, I've read a lot about using Windows servers as routers as being a BAD idea. And I'm willing to consider setting it up differently. All we really need are: AD DS accounts, Internet, and File Sharing (network drives to save files on). Of course group policy to manage the network with would be GREAT! But basically any setup that can get the big 3 (ADDS, Net, FS) working would be GREATLY APPRECIATED.
We have 4 switches in total connecting everything. The server is connected to the main 3com switch that is connected to the main IT office (which I cannot get help from as they are far too busy). The IT office provides the server (and a Linksys router) with Internet. The Linksys router is connected to the same switch. We use it to distribute Wi-Fi. Everything else cascades from the 3com.