Jump to content

Isn't 003 Router the Gateway not the DHCP ip's


Recommended Posts

Guest Irwin
Posted

1. Isn't '003 Router' the Gateway not the DHCP internal ip nic?

 

2. Do you know of any issues if I use more of the scopes options?

 

3. Does 'reservations' prevent assumed scope options?

 

4. Shouldn't I set smtp, wins, www, etc.,. because each client would know a

assumed 8day scope on topology of network.

 

5.Wouldn't this prevent less traffic?

 

6. Does 'reservation' use lease cost route per scope option?

 

7. Couldn't each client have more than one nic wh each nic have different

reserved scope options?

 

8. If I setup using the above networking topology. Wouldn't this give the

most optimal and secured network as far as DHCP assigning the scopes? (this

doesn't include any other layered hdwr, services, srvs., etc.,.

 

Thank you in advance! Irwin

  • Replies 1
  • Created
  • Last Reply

Popular Days

Guest Meinolf Weber
Posted

Re: Isn't 003 Router the Gateway not the DHCP ip's

 

Hello Irwin,

 

see inline

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> 1. Isn't '003 Router' the Gateway not the DHCP internal ip nic?

 

In the scope options form the DHCP server 003 is the Default gateway, the

ip address from the router in your network.

> 2. Do you know of any issues if I use more of the scopes options?

 

You can configure all options that are defined and that you really need.

Or what do you mean with the question?

> 3. Does 'reservations' prevent assumed scope options?

 

With a reservation you only "fix" an ipaddress to a MacAddress, the device

use the scope options from the scope where it is reserved.

> 4. Shouldn't I set smtp, wins, www, etc.,. because each client would

> know a assumed 8day scope on topology of network.

 

You should only set the needed options, that's all. Lease time is based also

on your needs and what you like to set, with laptops where people often move

around you do not need 8 day leases, when they stay only one day in the company,

just fills up your leases and blocks other devices, if you maybe run out

of ip's on the scope. With only desktops that never move you can set a longer

lease time.

> 5.Wouldn't this prevent less traffic?

 

The release of the ip address is a straight forward task, will not slow down

the network.

> 6. Does 'reservation' use lease cost route per scope option?

 

What do you mean with this?

> 7. Couldn't each client have more than one nic wh each nic have

> different reserved scope options?

 

A workstation normally have only one NIC connected to a network, more is

not necessary and with different ip's one one workstation you can become

problems with routing or accessing data.

> 8. If I setup using the above networking topology. Wouldn't this give

> the most optimal and secured network as far as DHCP assigning the

> scopes? (this doesn't include any other layered hdwr, services, srvs.,

> etc.,.

 

DHCP is always easy to configure, but to get control over connected machines,

it is more secure to use fixed ip's or use Vendor classes to only allow special

devices predefined in DHCP: http://technet2.microsoft.com/WindowsServer/en/library/13cbcfbd-2d9d-40fd-8b54-5c8090924eb21033.mspx

 

Additional you can also use manageble switches to allow only special MAC

addresses on the defined switch ports.

> Thank you in advance! Irwin

>


×
×
  • Create New...