[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] Okay let's duke it out... One nic or two? - THE OFFICIAL BLOG OF THE SBS "DIVA"
Sat, Jul 23 2005 13:10 bradley

Okay let's duke it out... One nic or two?

You heard me... we already had the Terminal server argument done to death..let's have the one nic or two religious argument.

I like two nics.  I like a separation from the internal and external network.  I like then having another small router on the outside for an additional onion layer.  I'm not a fan of a one nic, then external hardware firewall setup.  I can however, understand that folks consider this the more logical setup after coming from peer to peer.  I mean that's what they had in peer networks right?  Then you have all the confusion about this thingy called DNS and why does the router need to stop doing DNS and DHCP when it was doing it just fine before?

I've said it before on the blog that SBS and Active Directory [aka glue] works better when the SBS does the DHCP.  Why?  Because active directory would just logically handle services better on it's own platform than reaching out to ...say an external box.  The movement from peer to domain catches a lot of folks off guard because no longer do they point the DNS to the ISP's DNS but rather you now look inward and just use the ISP's DNS as forwarders in the Connect to Internet Wizard.  Changing from a setup that works...to one that is a bit of a hard one to get a handle on can be a hassle.

I'm going to go out on a limb here and say something controversial......[yeah, like that's a surprise]  I think the important thing is not necessarily one nic or two [even though I still would strongly argue for two nics and a RRAS+router or ISA+router], but rather that whatever firewall you pick that you monitor it and KNOW it.

One of the annoying things right now to me on ISA 2004 is that I'm not quite confortable with it and don't quite have the same level of knowledge of it as I did ISA 2000.  But I must say that what I like about it [and actually everything on SBS is in this category], because it is sitting on a box that I've turned on monitoring [or SBS's wizards have] and I've turned on it's reporting... I'm LOOKING at it.  People say that one of the problems with SBS is that 'it's all your eggs in one basket' but.... my view is that it's a basket that because of the monitoring tools... I'm looking at it a heck of a lot more than my member server.  If I had services and more redundancies, I don't have the monitoring in place on those redundant places [lord knows I don't on my member server which is something I need to fix].  I feel that BECAUSE it's all in one basket that I really pay attention to it much better than I would if it's services were strung out on several servers.  Call me crazy but I think... I feel... better about it because my 'attack surface' ...my 'threat model' is one that I monitor a lot more because of the SBS's monitoring emails that shove that data in my face.

In think the important thing isn't necessarily one nic or two...but rather the age old rule in protection your assets “KNOW THY SYSTEMS”.  If you don't know..don't patch..don't understand...don't monitor that firewall...don't watch the log files...... I don't think it matters a twit whether it's one nic or two.

So..let's have at is [and yes sorry I know the Captcha spam filter barfs a lot these days when you go to post back on the blog]...post your comments... one nic or two...and why do you choose that?  What is it about what you choose that makes it feel right to you?

Filed under:

# Mr

Saturday, July 23, 2005 2:52 PM by bradley

My vote is for two nics. I have a cable and a high speed wireless connection coming into a SonicWall (with failover on the wan connections). From there I connect to a wireless router (for internal wireless connections - I make the users vpn in to the SBS server if they need internal resources, and the external nic on my server. The internal nic then connects to the switch for internal users wired connections.

I like having the sonicwall as it provides a first layer of protection plus allows for site to site hardware vpn connections. The ISA server is a nice second layer to deal with the things that I allow past the sonicwall.

# Susan: Two NICs. And Live Logging is Win!

Sunday, July 24, 2005 12:34 AM by TrackBack

I was really trying to work an Animal Farm joke in here, but I can't make it work.
Susan brings up a...

# re: Okay let's duke it out... One nic or two?

Sunday, July 24, 2005 8:10 AM by bradley

From my experience, I have usually found it easier to configure SBS with a single NIC and use an external firewall to protect a network. It _can_ make using the VPN wizard more difficult, but overall it seems to work well.

However there are exceptions.

For my business, when speaking with a customer who is thinking about SBS, the deciding factor between an external firewall and using ISA Server is how concerned the business owner is with monitoring and controlling the Internet content that their employees see.

Since ISA Server forces everyone to log into it in order to access the Internet, this allows for very accurate reports to be generated on individual web surfing habits. It also allows for the creation of content filters that can be used to filter out web sites that a business owner might find objectionable (e.g. adult entertainment sites).

The downside to running ISA with SBS is that it takes SBS's already tremendous memory requirements, and makes them even larger. When running SBS Premium with all of its bits installed and operating, my partners and try not to configure systems with any less than 2.5 Gb of memory. (Otherwise these systems page like mad, and this can translate into slow web surfing via ISA Server.)

So to sum up:

If the business owner doesn't really care about where people are going on the Internet and isn't concerned about monitoring usage -- I would recommend saving yourself some hassle and memory, and using a single NIC with an external firewall.

On the other hand, if the business owner wants tight control over their employees Internet habits, then in my opinion running ISA Server with two NICs the perfect way to go.

# 2 nics

Sunday, July 24, 2005 5:13 PM by bradley

Easier to configure is no reason to choose single nic over two nics. Lack of knowledge on how to configure ISA only means that training is needed. ISA offers so much more than simply a measure of control over what end users are capable of seeing of the Internet. It's about security. It's all about securing SBS.

Regarding Sonicwall, when Blaster came out networks protected by sonicwall were vulernable if the port was open. Network protected by ISA weren't because ISA is smart enough to know the difference between legitimate traffic on a port and malformed traffic. It's take intelligence to fight the bad guys.

# re: Okay let's duke it out... One nic or two?

Monday, July 25, 2005 9:23 AM by bradley

This is also posted <a href=http://addicted-to-it.blogspot.com/2005/07/re-okay-lets-duke-it-out-one-nic-or.html>on my blog</a>.

As an SBS consultant, your biggest responsibility is conveying risk. At the end of the day, it's your customer's decision, your customer's data, and your customer's business that is at risk. So if you're out there accepting risk on behalf of the customer, without informing them of key decisions, you're simply not doing your job.

1 NIC or 2? I think it depends on your customer. Look at their environment, look at the budget, and then try to balance the needs of the customer with the needs of your employer. Customers are brining you in to help navigate confusing decisions on their behalf, and at the same time are trusting you to keep them in the loop on decisions that can have a material impact to their business. Beyond that, your employer is in business to make money. You can't risk loosing customers because you don't want to implement a 1 NIC install that is "less secure". And you typically shouldn't look at new installs from a break-even perspective. In most SBS environments that I've worked in, there's just not allot of money to throw around on high-end hardware. If you can do a 2-NIC install on a better platform great! But if the choice is between a 2-NIC install, and you/your employer making money, you've got to make money first to stay in business.

So bottom line... Actively communicate risk to your customer, balance the needs of your employer with the needs of your customer, and always protect your profit margin. After you take care of those things, then you can worry about the details.

# Building a box

Wednesday, July 27, 2005 6:00 PM by TrackBack

# Building a box

Wednesday, July 27, 2005 7:05 PM by TrackBack