Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm a Linux guy, but here at work we're basically re-doing our entire network and going to Active Directory. I'm trying to get Windows Small Business Server 2008 set up, and one of the problems I'm encountering is with the DHCP server.

We have 3 WAN connections. I want to take those three connections, plug them to our SonicWALL device, and from there each connection to a separate NIC on the SBS2008 server. Then I need the DHCP server to issue IP addresses in different subnets (,, depending on which NIC card the connection comes in on.

I need to allow these three subnets to communicate to the domain controller but NOT be allowed to communicate between the subnets. Those on shouldn't be able to ping devices on the and subnets.

share|improve this question

So you'll want to define 3 separate scopes: with nic 1 as the gateway with nic 2 as the gateway with nic 3 as the gateway

I'm assuming you'll probably use /24 subnets, but it doesn't really make a difference as long as they don't overlap. Since it's a Small business server and the DCHP server is also the AD server there should be no issues with the different connections getting to AD. I don't believe the different interfaces will be able to talk to each other, but I don't currently have a free test environment to verify with right now.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.