DHCP Scopes "Glenn" <nospam[ at ]yahoo.com> 12/30/2008 5:17:57 PM I'd appreciate some help with this... I am using the DHCP service on my Windows 2003 server. I had one scope on the server and one VLAN on my network (the default). The scope is 10.140.0.0 with a subnet mask of 255.255.240.0. I now have a new VLAN on my network (ID # 210). I've setup a new scope that I want to use on this VLAN. The scope will be 10.200.10.0 with a subnet mask of 255.255.0.0. I can't find out how to connect this scope to this VLAN. I made one port on my HP ProCurve switch untagged with the new VLAN (and tagged all of the rest of the ports with the new one). I plugged a laptop into it. It continues to get an IP address from the 10.140.0.0 scope (though it cannot access any network or internet resources). I knew it wouldn't get an IP from the new scope, because no where have I told it that the new scope (10.200.10.0) should be assigned to requests coming off of VLAN 210. Any suggestions? Thanks in advance.

Re: DHCP Scopes "Phillip Windell" <philwindell[ at ]hotmail.com> 12/30/2008 6:07:05 PM 1. Subnets should never be allowed to be over 250-300 hosts. So masks should never be lower than 255.255.255.0, which gives the perfect size of 254 hosts. Lower masks (containing more hosts) are for Supernetting over Backbones to keep routing tables smaller and more effiecient. 2. Switches are not routers. Simply creating VLans on a Switch does not truely give you real VLANs and does not give the means to route between them. It requires a Router or a Layer3 Switch to work properly. 3. In the case of Layer3 Switches,...these are Routers and Switches built into the same piece of hardware. But the Switching functions and the routing functions are still two different things and the Device needs to be "viewed" as two separate devices (router and switch) dispite the fact that it is all in the same physical housing. 4. With DHCP,...you simply create a normal, standard scope for the new subnet. Then configure the LAN Router to forward DHCP Queries to the DHCP Server. -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. ----------------------------------------------------- "Glenn" <nospam[ at ]yahoo.com> wrote in message news:%23ViKQKqaJHA.2620[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] > I'd appreciate some help with this... > > I am using the DHCP service on my Windows 2003 server. > > I had one scope on the server and one VLAN on my network (the default). > The scope is 10.140.0.0 with a subnet mask of 255.255.240.0. > > I now have a new VLAN on my network (ID # 210). > > I've setup a new scope that I want to use on this VLAN. The scope will be > 10.200.10.0 with a subnet mask of 255.255.0.0. > > I can't find out how to connect this scope to this VLAN. > > I made one port on my HP ProCurve switch untagged with the new VLAN (and > tagged all of the rest of the ports with the new one). I plugged a laptop > into it. It continues to get an IP address from the 10.140.0.0 scope > (though it cannot access any network or internet resources). > > I knew it wouldn't get an IP from the new scope, because no where have I > told it that the new scope (10.200.10.0) should be assigned to requests > coming off of VLAN 210. > > Any suggestions? > > Thanks in advance. >

Re: DHCP Scopes "Glenn" <nospam[ at ]yahoo.com> 12/30/2008 6:33:29 PM But I sitll don't get the connection. I could create 100 Vlans and 100 Scopes. How does the DHCP server know that something from VLAN # 3 should given an address from Scope # 57 for instance? "Phillip Windell" <philwindell[ at ]hotmail.com> wrote in message news:eYvNwlqaJHA.6036[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > 1. Subnets should never be allowed to be over 250-300 hosts. So masks > should never be lower than 255.255.255.0, which gives the perfect size of > 254 hosts. Lower masks (containing more hosts) are for Supernetting over > Backbones to keep routing tables smaller and more effiecient. > > 2. Switches are not routers. Simply creating VLans on a Switch does not > truely give you real VLANs and does not give the means to route between > them. It requires a Router or a Layer3 Switch to work properly. > > 3. In the case of Layer3 Switches,...these are Routers and Switches built > into the same piece of hardware. But the Switching functions and the > routing functions are still two different things and the Device needs to > be "viewed" as two separate devices (router and switch) dispite the fact > that it is all in the same physical housing. > > 4. With DHCP,...you simply create a normal, standard scope for the new > subnet. Then configure the LAN Router to forward DHCP Queries to the DHCP > Server. > > > -- > Phillip Windell > www.wandtv.com > > The views expressed, are my own and not those of my employer, or > Microsoft, > or anyone else associated with me, including my cats. > ----------------------------------------------------- > > > "Glenn" <nospam[ at ]yahoo.com> wrote in message > news:%23ViKQKqaJHA.2620[ at ]TK2MSFTNGP02.phx.gbl... >> I'd appreciate some help with this... >> >> I am using the DHCP service on my Windows 2003 server. >> >> I had one scope on the server and one VLAN on my network (the default). >> The scope is 10.140.0.0 with a subnet mask of 255.255.240.0. >> >> I now have a new VLAN on my network (ID # 210). >> >> I've setup a new scope that I want to use on this VLAN. The scope will >> be 10.200.10.0 with a subnet mask of 255.255.0.0. >> >> I can't find out how to connect this scope to this VLAN. >> >> I made one port on my HP ProCurve switch untagged with the new VLAN (and >> tagged all of the rest of the ports with the new one). I plugged a >> laptop into it. It continues to get an IP address from the 10.140.0.0 >> scope (though it cannot access any network or internet resources). >> >> I knew it wouldn't get an IP from the new scope, because no where have I >> told it that the new scope (10.200.10.0) should be assigned to requests >> coming off of VLAN 210. >> >> Any suggestions? >> >> Thanks in advance. >> > >

Re: DHCP Scopes "Phillip Windell" <philwindell[ at ]hotmail.com> 12/30/2008 7:23:34 PM "Glenn" <nospam[ at ]yahoo.com> wrote in message news:OGnse0qaJHA.4288[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > But I sitll don't get the connection. > > I could create 100 Vlans and 100 Scopes. > > How does the DHCP server know that something from VLAN # 3 should given an > address from Scope # 57 for instance? That is a combination of the Router forwarding the queries to the DHCP Server and the way the DHCP Service "handles" the forwarded queries. That has been one of a LAN Router's "jobs" since TCP/IP was invented. The router may include additional information in the forwarded query that the DHCP Service uses,...I don't know for sure,....but it "just works". There is nothing special that you have to configure beyond setting the router to forward the queries.. .....and, before you ask or think about it,....No SuperScopes!!!,....use just normal, regular, "nothing special" Scopes for each subnet. -- Phillip Windell www.wandtv.com The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. -----------------------------------------------------