Server 2012 essentials with dual NIC?

ubersonic

ubersonic

ubersonic

Soldato
Joined
26 May 2009
Posts
22,164
Hi all, our current network setup is this:

IC179798.gif


However looking at all the info for Server 2012 essentials it seems to like just having one NIC and plugging straight into the switch with the client PC's. Is it possible to do it the old way? I would much prefer to do it that way for ease/simplicity if possible.

Thanks

For reference in the diagram the external NIC and router use static public IP's (as do other servers connected to the router) and the internal NIC and clients use private IP's.
 
When you say not supported do you mean it doesn't work or that it's not MS's recommended solution? Don't really want to shell out for full blown Server 2012 if I can avoid it.

Thanks.
 
I don't want to sound dumb here, but how is an SBS2003 to essentials 2012 migration even possible (I know it is as people have done it) if essentials can't use the same topology as 2003? how can they physically coexist? :confused:

If I enable NAT on the router to make essentials work then that will screw up the 2003 servers connected to it.
 
Thanks dude, so let me see if I understand this right, the servers and clients all connect to the router (via switches and whatnot) and the router controls DHCP, the servers like the clients are set to receive DHCP addresses instead of static and the router is set to assign them public addresses (identifying them by their MAC) and the clients private addresses. Running NAT for the clients but not for the servers.

Have I got that right (sorry I have never set a network up like this before).
 
Thanks for the help guys, can somebody help clarify to me how I go about setting up the following using the modern topology:

I want the Essentials 2012 box (Main network server) and a Server 2008 R2 Standard box (DNS name server for the domain) box connected using static IP's so they can be seen properly from the outside world. One of my routers (a BT Business Hub 3 made by 2wire) manuals says it can do this by assigning those machines DHCP addresses from my public IP pool, and the rest of the clients private IP's.

My issues though are, in order to make local DNS work properly for the clients/essentials the DHCP on the router will need to specify the essentials box as the primary server no? but then the external DNS server will get that DHCP setting too, and bah.

One idea I had was to keep the current setup of router routing public IP's, but instead of it going through the SBS2003 machine to the local network put another router in that place with the connection to the first router was WAN, that way it will appear to the stuff connected to router 2 that they are alone on a normal one router network (don't know if any of this makes sense :(
 
Hi, thanks that's very informative, what I meant by the bit you quoted was that one of the machines is a DNS nameserver for a web domain. I was unsure how that getting DHCP (and DNS settings from DHCP) would interact with that.
 
You must log in or register to reply here.
Back
Top Bottom