The Official SBS Blog : You May Lose the Default Gateway on SBS 2008 Every Time You Reboot:

The Official SBS Blog : You May Lose the Default Gateway on SBS 2008 Every Time You Reboot:
http://blogs.technet.com/sbs/archive/2010/04/22/you-may-lose-the-default-gateway-on-sbs-2008-every-time-you-reboot.aspx


 



I’ll be honest, I don’t see this on all of my SBS 2008 boxes.. actually I’ve not seen this on any under my wing, so it’s not something that occurs on all SBS 2008 servers.

One Thought on “The Official SBS Blog : You May Lose the Default Gateway on SBS 2008 Every Time You Reboot:

  1. Joe Raby on April 27, 2010 at 4:01 pm said:

    I was setting up a WDS deployment server in another room where there’s no wired LAN, so I decided I’d use that Windows Server 2008 R2 Enterprise license in my Action Pack that I never got to use yet. It’s a pretty low-end system – an Atom dual-core system – but it works just fine for our few instances that we use WDS.

    Anyway, we had set up a WLAN adapter to connect to our SBS network, and used RRAS with the wired NIC (set to 192.168.0.2) to segment our deployment targets on a separate subnet. It’s pretty much exactly like a dual-NIC SBS 2003 setup, except without Exchange and SharePoint. It runs a completely separate deployment domain with DNS and DHCP, and the deployment server “sees” our SBS network as being “the internet”, even though it really isn’t. I had a spare Linksys 4-port router laying around, so I turned off wireless, assigned the IP address to it that we wanted (192.168.0.1 for ease of use), turned off DHCP on the router (server’s doing that job), and disabled NAT in the Advanced Routing settings. Now it’s a 4-port switch or our “internal” network. ;)

    Anyway, there’s a document on Microsoft’s site about setting up WDS with Server 2008 (R1), but it says that DHCP doesn’t need to have a Default Gateway set up in the Add Role screen.

    In Server 2008 R2 with this kind of setup, it doesn’t work. DHCP will assign an IP address through the “router” (now just a switch, but with an IP address in the same subnet as the internal network so the web-based config can still be accessed). Clients won’t receive any internet access. It’s not that they’re seeing the router/switch and getting confused – they just don’t see any gateway at all. Clients need to have Option 3 set up in DHCP – that’s the “Router” setting, AKA “Default Gateway”. Without it, DHCP clients don’t know where to go to get internet access.

    So word of advice: In Server 2008 R2, when you’re setting up DHCP, make sure you specify a default gateway in the Add Role wizard for it if you want clients to have access to the internet, even though the description says it’s optional. You’ll thank me for it.

    FYI: I plan on documenting the setup (later) for budding System Builders.

Post Navigation