Re: Dual NIC vs Single NIC



Joe <Joe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
In the past Most of my systems have been dual NIC usually with ISA
but due to many reasons I am now considering going to a single NIC
and moving away from ISA.

Currently with my existing setup, if the SBS server is down, for what
ever reason, my customers can't even get to the internet.

Yes they can.....they just can't resolve names :)

If I had a second member server set up as the backup DC, a single NIC
SBS server, and a hardware firewall wouldn't that allow my customer
to log on and access the internet if the SBS server was offline
temporarly? I would still want the SBS server to run the DHCP and DNS
roles but would assume that would not matter as long as the SBS
machine was not down for more than a few hours at a time.

Yes. If you have another DC running AD-integrated DNS, and your client
workstations have the secondary DNS server listed, they should work.

The above seems logical to me, but then since I have not done it I am
checking for any "gotchas" lying around that I might not be aware of.

By the way I would be running SBS2003R2 on such an install that would
assist me in the licencing issue of the second server which would be
running server 2000 or 2003 as a member of the SBS box.

You'd need to buy Windows 2000 or 2003 but I believe you wouldn't need
additional CALs.

That all being said, if you're having regular problems with your SBS box
going down, I'd rather address those - add as much redundancy to the server
hardware as you can. That would be a better use of money, in my opinion,
although it's true that outside of SBS, it's always recommended to have more
than one DC.


Joe



.



Relevant Pages

  • Re: Outlook 2003 cant see Exch 2003 over RPC
    ... I even went the whole hog and made the SBS box the DHCP and DNS for the LAN, ... Disk shares, net view, etc work between the same workstation and the server, ... I did briefly get Outlook RPC over HTTP to work, ... Router as DHCP Server but DNS must be handled by SBS Server for everything ...
    (microsoft.public.exchange.setup)
  • Re: Suggestions for networking book
    ... I've set up my own DHCP server today, but would like to know enough about the others that I can configure them myself, gain some experience and perhaps use that in a job interview. ... It isn't a complete guide to all the snags and details of DNS and its server implementations. ... think it might be the most useful to know about, given my reasons above. ... exim book is pretty well written and has a lot of relevant examples. ...
    (comp.unix.admin)
  • Re: Slow logons / Slow Pings to Server / NSLookUp fails
    ... "The SBS server provides DHCP and DNS, which includes entries in the DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: Registered domain name not translating internally
    ... Once you fix your DNS, clear your Event Viewer logs, then your dcdiag output ... When you do an nslookup, it should find your server if you have a reverse ... SBS Server is setup with one NIC. ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS Error
    ... Are you saying all your units have PUBLIC or PRIVATE static IPs and if you've got workstations pointing to anything other than the SBS server, then this outside the recommended configuration most likely why your having issues. ... I only have 3, but it allows me to set an alternate DNS server to the router in case the server goes down, my clients will still have an internet connection. ... For a DHCP client, please make sure the Option 15 DNS domain name is ...
    (microsoft.public.windows.server.sbs)