I would second that. Using the DHCP option for remote clients was
designed to allow easy setup for people with limited networking knowledge.
Because the remotes are in the same IP subnet, the server acts as a proxy
for them on the LAN.
In anything other than a simple one-segment LAN, put the remotes in
their own subnet and route them just as you would route an additional LAN
segment.
Neteng wrote:
> Yes that is what I meant, but since you'll be using VPN, you can do
> can assign a completely different subnet (from the VPN device) to the
> VPN clients and allow that traffic to your internal network.
>
> "Jeff" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> On Wed, 12 Apr 2006 14:00:38 -0500, "Neteng" <(E-Mail Removed)>
>> wrote:
>>
>>> It would be best to create multiple Class C networks.
>>>
>>> "Jeff" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> I am going to change our internal ip range and would like to have
>>>> more than 253 addresses avaliable. Would it be better to go with a
>>>> supernet class C 192.168.0.0/23 setup or or go with a class B
>>>> 172.20.0.1/23 configuration. We are running Windows 2003 servers
>>>> and all of the workstations are 2000 sp4 and XP Pro sp2.
>>>>
>>>> Thanks for any help.
>>>
>>
>>
>> When you say multiple Class C networks are you talking about two
>> Class C networks split by a router? Just wondering because at the
>> present time I have about 200 devices and I wanted extra IP's
>> because I will be implementing a VPN for mobile users that will pull
>> IP's from a DHCP server and I wanted enough to go around with some
>> extra room on top of that.
>>
>> Thanks
|