B networks have a lower routing priority when a router makes routing
decisions because it would be a shorter match than a C network. If you want
to get technical, you have a 10.0.0.0 Class A network subnetted with 16
bits, in 3 subnets and also subnetted with 8 bits in one subnet. With your
current design, the Sursee office computers will think that all the
computers in the Winterthur, Bern and Basel are local. I said computers,
not the router. I'm not going to go into the routing details. To say the
network design is supported would only be if you don't want the Sursee
network host to communicate with the other 3 networks.
The reason I gave my last response is because of the method a Windows
computers uses to request a DHCP IP address. The networks overlap. A
computer from one of your three remotes sites when connected to the Sursee
network will attempt to allocate the IP it allocated previously. That IP
address would be legitimate in the Sursee network. I have see issues with
DHCP address assignment and subnet length and thought it best to resolve the
network overlap before proceeding with DHCP troubleshooting.
"C.Addario" <(E-Mail Removed)> wrote in message
news:BBD303F9-C6D8-4DBA-A9F6-(E-Mail Removed)...
> Hello Jeremy, Joshua
>
> 1st. DHCP traffic can't pass the WAN link
> 2nd. This is a full supportet network configuration, because the B network
> has a lower routing priority than the C networks.
>
> The problem is the dhcp/client configuration, if i manualy enter "ipconfig
> /renew" the client get a new IP.
>
>
> Thanx Claudio
>
> "Jeremy Church" wrote:
>
>> A larger problem is your remote networks 10.236.10.0/24, 10.236.11.0/24
>> and
>> 10.236.12.0/24 overlap with the 10.236.0.0/16 network.
>>
>> I would clear up the IP range overlap and then troubleshoot the DHCP
>> leasing
>> issue. Who knows, it may even clear the DHCP issue up.
>>
>>
>> "C.Addario" <(E-Mail Removed)> wrote in message
>> news:7E6FF029-C700-404F-8184-(E-Mail Removed)...
>> > Hello we have a special network configuration between our offices in
>> > swizerland.
>> >
>> > In the main Office Sursee we have a Client VLAN 236 with the Network
>> > 10.236.0.0 mask 255.255.0.0
>> > The Office Winterthur is connected with 4MB/s with the Network
>> > 10.236.10.0
>> > mask 255.255.255.0
>> > The Office Bern is connected with 4MB/s with the Network 10.236.11.0
>> > mask
>> > 255.255.255.0
>> > The Office Basel is connected with 4MB/s with the Network 10.236.12.0
>> > mask
>> > 255.255.255.0
>> > All sites have their own DHCP Servers.
>> >
>> >
>> >
>> > Now, if a User comes from Winterthur, Bern or Basle to Sursee or in
>> > reverse,
>> > he don't renew the whole DHCP configuration!
>> >
>> > For example a User from Bern has the following configuration:
>> > ip 10.236.11.50
>> > mask 255.255.255.0
>> > Gateway 10.236.11.1
>> > DNS 10.235.14.14
>> > WINS 10.235.14.14
>> >
>> > Now he comes to Sursee, he connect the Network and now he has the
>> > following
>> > configuration:
>> >
>> > ip 10.236.11.50
>> > mask 255.255.255.0
>> > Gateway 10.236.1.1 <- Just the Gateway changed!
>> > DNS 10.235.14.14
>> > WINS 10.235.14.14
>> >
>> > If he makes an ipconfig /renew it get a new correct ip per example:
>> >
>> > ip 10.236.80.72
>> > mask 255.255.0.0
>> > Gateway 10.236.1.1
>> > DNS 10.235.14.14
>> > WINS 10.235.14.14
>> >
>> >
>> > Thanx for your help...
>>
>>
>>
|
Similar Threads
Linear Mode
