DHCP options for a new DC/DNS/DHCP

Discussion in 'Windows Networking' started by Sam, May 13, 2005.

  1. Sam

    Sam Guest

    Hi,

    I just setup the first server of a new W2K3 network. What DHCP options
    should I select? The network will have ISA 2004 w/ Internal, External and
    DMZ, Exchange 2003, SQL 2000 and Windows XP Pro clients. The network will
    start small but grow in time. I want everything to be 100% by the book.

    Thanks,


    Sam
     
    Sam, May 13, 2005
    #1
    1. Advertisements

  2. Start simple:

    Router (Default Gateway) = Option #003
    DNS Server = Option #006
    WINS Server = Option #004
    WINS Node Type = Option #046 (typically it is "0x8" more often than not)

    When creating Scopes, use the *entire* IP# Range. Then use Exclusions to
    limit which addresses you want it to give out. So if your LAN uses
    192.168.1.0/24 then the full range is 192.168.1.1 -- 192.168.1.254.

    I usually Exclude the fist 25 addresses and the last 25 addresses. The first
    25 are used for network Devices (Servers, hubs, switches, routers). The last
    25 I use for Printers and any other "leftover" devices.

    Don't confuse Exclusions with Reservations.

    Keep Reservations to an absolute minimum. Remember that even though a
    Reserved Address behaves as a Static Address it is still not Static, it
    *still* depends on DHCP and if the DHCP Server goes down it can put devices
    using those addresses out of business. So all Servers, Printers, and
    Infastructure Devices should use Static Addresses and not depend on DHCP.
    Keeping Reservations to a minimum also simplifies replacing the DHCP Server
    in the future because you won't need to do any "migration",...you'd just
    build the new one, create the Scope with the same "specs", shutdown the old
    one and "let'er rip".

    The best way to be 100% by the book is to keep the book small and simple.

    The more complex you make it the greater chance of a screwup and the more
    complex it is the more difficult it becomes to find that screwup when it
    happens.
     
    Phillip Windell, May 13, 2005
    #2
    1. Advertisements

  3. Sam

    Guest Guest

    just curious....
    why are we all still using wins when its likely not necessary most of the
    time? for example this small network will likely have 1 subnet, 1 gateway
    (router), and will likely stay that way forever. in this case wins is
    completely unnecessary. and i would even argue that its unnecessary in ANY
    environment.



     
    Guest, May 13, 2005
    #3
  4. 1. Exchange Clients run better with it and sometimes not at all without it.
    2. Network Browsing (Network Places, Network Neighborhood) require it when
    running a multi-subnet network.
    3. Using "single word" (netbios machine names) names in UNC paths to access
    machines require it if passing over routers.
    4. Probably more,...but that is what comes to mind off the top of my head.

    --

    Phillip Windell [MCP, MVP, CCNA]
    www.wandtv.com


     
    Phillip Windell, May 13, 2005
    #4
  5. Sam

    Guest Guest

    right. but 75% of your answers deal with multiple subnets across routers.
    since 2000 pro the OS is perfectly capable of resolving netbios names via
    dns. and unless we're talking exchange 5.x, outlook functions fine without
    wins. if this guy has 2000 or 2003 servers, no 98 clients, 1 subnet (all
    likely) wins is an unnecessary complication for him.


     
    Guest, May 13, 2005
    #5
  6. Sam

    Sam Guest

    Phillip,

    First, thank you very much for your response. I was also going to ask about
    WINS but you pretty much answered my question before I asked it.

    I think there may be one more reason for WINS. I had a situation in a W2K
    network where people who VPN'ed into the system could only find computers,
    servers, etc. w/ their IPs not by device name. Do you think WINS or lack
    thereof in that particular network had any role in this?

    Thanks again.

    Sam


     
    Sam, May 13, 2005
    #6
  7. Sam

    Guest Guest

    still dont need wins. to fix this simply set the dns server for the vpn
    connection to use the dns server on the network. now once the vpn client
    connects, it will use an internal dns server and resolve names the way it
    should, via dns

    :)


     
    Guest, May 13, 2005
    #7
  8. That isn't entirely true with Outlook, but I don't have any details close at
    hand right now.
    But we don't know that he has it that way with all newer OSs, and WINS is so
    extremely simple it doesn't complicate things to begin with.
     
    Phillip Windell, May 13, 2005
    #8
  9. Theoretically DNS would handle it, but WINS is ridiculously simple to setup
    and has very little over head,...Just use both and forget it,...then you
    won't have to worry about it,...unless you can say with absolute certainty
    then there will never, ever, ever, be any possibility of a Win98 machine
    being used via VPN or a NT machine being used on the LAN.

    Exchange and Outlook can still have problems without WINS inspite of MS's
    attempts to ween it from WINS. I was told that last time I was at one of our
    meetings in Redmond although I no longer have any specific details on that.
     
    Phillip Windell, May 13, 2005
    #9
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.