DNS Server Event 407/408/404
I have SBS 2008 and installed a second dual NIC card. The goal is to have the two built-in ports for the physical server and the other two ports for a Hyper-V virtual server. I realized that I now have the mentioned event errors. I wonder if there is some conflict with the setup of those NIC cards. I currently have: NIC1: IP=xxx.xxx.xxx.251, Gateway=xxx.xxx.xxx.249, DNS=126.96.36.199 NIC3: IP=xxx.xxx.xxx.252, Gateway=xxx.xxx.xxx.249, DNS=188.8.131.52 NIC2&4: Not connected Could it be an issue that the gateway is the same? If so what should it be? I am also not sure about the google DNS. The SW I need to install (Dynamics CRM & ADFS) requires some DNS settings to point to each other. So should the first DNS entry for the NIC point to something else? Btw, we have our domain with godaddy and there we have certain subdomains pointed to the above servers. These are the subdomains required by the software to be installed.
March 10th, 2012 1:47pm
SBS 2008 does not support two network cards you should only have one enabled. http://blogs.technet.com/b/sbs/archive/2008/09/16/sbs-2008-supported-networking-topology.aspx SBS server should be pointing to itself for DNS only as well
March 10th, 2012 3:07pm
Thanks. That is very disappointing and surprising. That leads to the following questions: * If I buy Server 2008 can I still use SBS 2008 to host for instance CRM/SQL or will SBS trying to take over as a domain controller or otherwise run havoc? * Why does SBS2008 Prem come with a regular and virtual license key? Are you only supposed to use one at any time? * I assume the virtual SBS install typically goes on another Windows server. Wouldn't that cause problems with SBS being on the same network as that server?
March 10th, 2012 4:23pm
Read over this. http://technet.microsoft.com/en-us/library/dd239208(v=ws.10).aspx Your answers are in the link. You get a virtual license or a physical license of SBS which means you can install SBS 2008 on a physical server or you can install as a virtual machine but not both. You have an extra license for Windows 2008 Server Standard as well so, you can install this license to run both SBS 2008 and Windows 2008 Server Standard. Your SBS 2008 Server will still need to be the domain controller that holds all fsmo roles. Your Windows 2008 Server install can then be a member server of that domain or a domain controller but either way two network cards enabled running their own IP address is not supported on a Domain Controller or recommended. Having multiple network cards running on a DC will cause DNS issues. You can get around the DNS issues by going through some steps but it is still NOT recommended or supported. SBS can run with multiple other servers on the same domain. SBS doesn't limit you to only run one server but it must hold all FSMO roles for the domain
March 10th, 2012 4:49pm
Thank you! I did go through many of the pages there with the most helpful one being here http://technet.microsoft.com/en-us/library/dd239197(v=ws.10).aspx It seems I can 1) Install Windows Server 2008 Std \w SP2 on the physical server \w or \wo GUI (my choice) 2) Create a virtual PC and install the same OS as in 1) 3) Create a virtual PC and install Windows SBS 2008 So basically there are three OSs but according to the license I can use 1) only as a host with no other program installed. That brings me back to the NIC cards. Hyper-V wants you to define a NIC. I guess 1) does not need network access as it's just a host. But 2 and 3 need it. I believe this should not be a problem because 1) supports multiple NICs and the virtual PC for SBS only will see one NIC (as defined when creating the virtual PC). Is this correct?
March 10th, 2012 5:55pm
Your Host supports multiple NICs but your host will not be SBS but the Windows 2008 Server Standard which supports multiple network cards. The host needs one network card and your Virtual machines can share one network card or have a dedicated card for each of the VM so, if you use dedicated cards you will need to have at least three network cards. Your host will only be a Hyper-V Host server you will not have any services running on this server like AD Services. Hyper-v networking docs. http://blogs.technet.com/b/jhoward/archive/2008/06/16/how-does-basic-networking-work-in-hyper-v.aspx http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/01/08/understanding-networking-with-hyper-v.aspx
March 10th, 2012 7:32pm