Thanks Mike, I thought that was going to be the ultimate answer... I should
just point out that the chapter in the MCSE Texts are way off on ths one...
Guess I'll be in here over the weekend configuring a VLAN. Thanks
--
----------------------------------------------------
This mailbox protected from junk email by MailFrontier Desktop
from MailFrontier, Inc.
http://info.mailfrontier.com
"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Bill,
>
> What you see is expected if you put two DHCP servers on same networks. If
> client broadcasts DHCP discovery and there are two DHCPs on the network it
> will use the one that will respond first. If you want to prevent this, you
> will have to configure VLAN on your switch or router between the networks.
> NetBIOS name has nothing to do with this...
>
> Mike
>
> "Bill Lucas" <wcluREMOVETHIScas AT COOL BLUE DOT COM> wrote in message
> news:%(E-Mail Removed)...
>> Hello as our company continue to grow we are forced with retooling our
>> network. While most things have been going smoothly I am having a DHCP
>> Issue which I do not know if there is a solution for...
>>
>> We currently have our Primary Domain 192.168.1.0 and we are configuring a
>> lab domain 172.16.1.1 - 172.16.2.255 for testing... we exceeded the
>> 255 IPs offered in the 192.168.1 subnet and are moving to the new range
>> specified.
>>
>> The issue is with the DHCP servers. Every time we bring the DHCP Servers
>> for the Lab domain online our clients are picking up addresses for this
>> network range. I looked through my MCSE books and I thought I had the
>> servers set up ok.
>>
>> Current lease times I think are 14 days but whenever a lease expires it
>> is not renewing its existing address and getting a lad address. I
>> configured our Primary DHCP Server with 2 scopes. The first was the one
>> existing to service the 192.168.1.0 subnet and the second range is the
>> new lab domains range of 172.16.1.1 - 172.16.2.255. the Lab scope has an
>> exclusion range covering 100% of the available IP Addresses. The DHCP
>> servers for the lab domain have the exact opposite set up. first scope
>> will service 172.16.x.x and the second scope is the 192.168.1.0 scope
>> with an exclusion range of 100% of the IP addresses.
>>
>> As I thought I understood this, it would prevent Nak messages from the
>> NEW DHCP servers but still not grant IP information in that scope...
>> Well I am guessing that is right as I don't see any Nak messages but it
>> is resetting the address which is not the desired outcome. I would have
>> used an 80 / 20 split between the two scopes but our primary scope is so
>> full and servicing clients I didn't want to mess with it. there isn't a
>> contiguous block of IPs that I could section off to the new scope.
>>
>> Any bright thoughts on this or am I going to have to decide between using
>> static IPS in the lab setting or trying to mess with our production
>> switch to get a new VLAN set up for the lab domain. not a desirable
>> thing because of the change control on the switch.
>>
>> Don't know if this is important or not but the person who set the lab
>> space up used the same NETBIOS domain name as the primary domain, and we
>> would have to redo all the lab configuration to change that (not
>> desirable either way I know)
>>
>> Thanks,
>> Bill
>>
>> wc_REMOVETHIS_lucas @ cool blue dot com
>>
>>
>>
>>
>
>
Similar Threads
Linear Mode
