Welcome to Sign in | Join | Help
in
Home Blog Forums

Windows Server 2003 DHCP

Last post 06-18-2007, 12:22 PM by kseventy. 5 replies.

Sort Posts: Previous Next
  •  04-16-2007, 10:39 AM 472

    Windows Server 2003 DHCP

    Hi,

    Congratulations on the new site migration it looks and works awesome!! Big Smile

    Anyway i've just redone our office internal network as follows:

    172.16.0.x - Routers, switches, printers, etc....
    172.16.1.x - Servers
    172.16.2.x - Hard cable computers and laptops.

    What im wondering is using DHCP on win2k3 is it possible to assign the 2.x range to all the desktop/hard cabled devices and assign the 3.x range to all wireless clients in the building,
    at the moment the DHCP server hands out the 2.x range to all machines.

    Would it also be possible (for another scenario) to have say 2.x range to one side of the building and 3.x range to the other side? i assume VLANing will come in here somewhere.

    Kind Regards,
    Duncan.
     

    Filed under: , ,
  •  04-16-2007, 11:45 AM 476 in reply to 472

    Re: Windows Server 2003 DHCP

    Might this post help?

     http://thelazyadmin.com/blogs/thelazyadmin/archive/2007/02/08/DHCP-User-Classes.aspx

     


    Daniel Nerenberg
    LazyAdmin
    MCT,MCSE,MCTS,MCITP
  •  04-16-2007, 12:02 PM 477 in reply to 476

    Re: Windows Server 2003 DHCP

    Yeah that's what inspired this post Smile , i was just wondering how do i implement that to do what i want? it's great for changing DNS servers and other scope options on a per machine or per segment/ad group basis but i can't see how it can give out differernt ip range's ?

    maybe you could write a tutorial Big Smile

    thank's in advance.
  •  04-19-2007, 7:48 PM 566 in reply to 477

    Re: Windows Server 2003 DHCP

    Hi Duncan,

    What you're talking about (giving IP addresses to machines with DHCP for different subnets) is typically done with VLANs and routing hardware. For example you could make all your wired clients 172.16.2.0/24, all your wireless clients 172.16.3.0/24 etc and then because these devices would be on different logical networks (or subnets), that is where the routing comes into play.

    Any broadcasts that a client on for example the wired subnet (172.16.2.0/24) would send out will have VLAN information along with it which would be then passed on to your DHCP server. The DHCP server would then assign an address from the proper range based on that.

    Maybe i'm thinking too much above this but i'm pretty sure this needs to be accomplished through hardware.

     - Dave


    Certs: CCNA, Network+
  •  04-20-2007, 6:02 AM 573 in reply to 472

    Re: Windows Server 2003 DHCP

    Duncan:

    What im wondering is using DHCP on win2k3 is it possible to assign the 2.x range to all the desktop/hard cabled devices and assign the 3.x range to all wireless clients in the building,
    at the moment the DHCP server hands out the 2.x range to all machines.

    Would it also be possible (for another scenario) to have say 2.x range to one side of the building and 3.x range to the other side? i assume VLANing will come in here somewhere.


    Part 1: I think no, because the DHCP server just assigns addresses one after another and I don't believe there is any way for it to differentiate between wired or wireless. The 2k3 DHCP will even assign addresses to clients on separate subnets if that's how it has been setup i.e. the server is on 192.168.0.1 but gives out DHCP addresses of 10.0.0.x even though afterwards the clients can't talk to the DHCP server.  The only thing, It think, would be to have two DHCP servers serving on either side of a router (or something like vlan routing on a switch) like Dave states.

    Part 2: The fun with that would be getting the same subnet to talk across a router. Would be best to have them as /24 rather than /16 then they would know to use the router. 


    cheers
    Andy
  •  06-18-2007, 12:22 PM 875 in reply to 573

    Re: Windows Server 2003 DHCP

    I have managed this in the past by assigning a static IP in the 3.x range to the Wireless AP/Router. All requests then come via the 3.x range for wireless with relevant replies. I did find that other problems occurred though, so test it first.
View as RSS news feed in XML


All postings are provided "AS IS" with no warranties, and confer no rights.
Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.