DHCP reservations active/inactive

[Guest]

Archived from groups: microsoft.public.windowsnt.protocol.tcpip (More info?)

I have a LAN with +- 500 pc's. We work with DHCP on a Windows 2003 server.
Every pc gets a dhcp-reservation according his MAC-adress. Once a pc
activates his reservation, it stays active for ever. But pc's come and go.
New pc's are no problem for a new reservation because I know the new pc's.
But when an old pc leaves the network, I can't see that because the
reservation stays active. Is there a way to deactivate a reservation
automatically when its not used for a long time? Or even to delete the
reservation automatically?

Please help because my IP-range is running out of place.

 

[Guest]

Archived from groups: microsoft.public.windowsnt.protocol.tcpip (More info?)

"Bart Vanhoutte" <bart.vanhoutte@skynet.be> wrote in message
news:4180bfef$0$25831$ba620e4c@news.skynet.be...

> I have a LAN with +- 500 pc's. We work with DHCP on a Windows 2003 server.
> Every pc gets a dhcp-reservation according his MAC-adress. Once a pc
> activates his reservation, it stays active for ever. But pc's come and go.
> New pc's are no problem for a new reservation because I know the new pc's.
> But when an old pc leaves the network, I can't see that because the
> reservation stays active. Is there a way to deactivate a reservation
> automatically when its not used for a long time? Or even to delete the
> reservation automatically?
>
> Please help because my IP-range is running out of place.

I sorta wonder if we have a language problem here. Because if we don't, why
on earth are you using DHCP reservations rather than leasing dynamically
allocated addresses?? Put it another way: is there any reason at all from
the PCs' point of view why, once given an IP address, they must have the
*same* IP address till the end of eternity? Most PCs in client roles are
quite happy to use any IP they're given, and if they get a different IP
address tomorrow, who notices or cares?

--
rgds
David Brownridge

 

[Guest]

Archived from groups: microsoft.public.windowsnt.protocol.tcpip (More info?)

We care because of the following reason: security. We are here in a company
with quite often some visitors. We know from the past that they can be a
source of virus-outbreaks. Therefor we work with Vlan's. Only the pc's from
the employees that we know, get a reservation in the Vlan of our network. So
they get access to all the network resources we have. 'Strange' pc's get a
IP-adres in an other Vlan so they can only access the internet and do not
get access to our own networkresources. In that way they can not infect our
network. Also the pc's that our developpers or engineers bring from home or
I don't know where from, cannot get on the network. This still remains more
dynamic then when we should disable the dhcp-service and give them all a
fixed IP-adres. And there are also some applications running here over the
network that need the same IP-adres for a pc for eternity.
I hope this brings some more explanation.

kr
Bart Vanhoutte

"David Brownridge" <DVD@melbpc.org.au> wrote in message
news:%23uSrqbNvEHA.200@TK2MSFTNGP11.phx.gbl...
> "Bart Vanhoutte" <bart.vanhoutte@skynet.be> wrote in message
> news:4180bfef$0$25831$ba620e4c@news.skynet.be...
>
> > I have a LAN with +- 500 pc's. We work with DHCP on a Windows 2003
server.
> > Every pc gets a dhcp-reservation according his MAC-adress. Once a pc
> > activates his reservation, it stays active for ever. But pc's come and
go.
> > New pc's are no problem for a new reservation because I know the new
pc's.
> > But when an old pc leaves the network, I can't see that because the
> > reservation stays active. Is there a way to deactivate a reservation
> > automatically when its not used for a long time? Or even to delete the
> > reservation automatically?
> >
> > Please help because my IP-range is running out of place.
>
> I sorta wonder if we have a language problem here. Because if we don't,
why
> on earth are you using DHCP reservations rather than leasing dynamically
> allocated addresses?? Put it another way: is there any reason at all from
> the PCs' point of view why, once given an IP address, they must have the
> *same* IP address till the end of eternity? Most PCs in client roles are
> quite happy to use any IP they're given, and if they get a different IP
> address tomorrow, who notices or cares?
>
> --
> rgds
> David Brownridge
>
>
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsnt.protocol.tcpip (More info?)

Those systems that need a fixed IP can be given reserved IPs or IPs that
are excluded from normal allocation. If you give leases a lifetime of,
say, a month, and those machines periodically renew their leases within
that time, they would normally keep the same IP.


--
#include <standard.disclaimer>
_
Kevin D Quitt USA 91387-4454 96.37% of all statistics are made up
Per the FCA, this address may not be added to any commercial mail list

 

[Guest]

Archived from groups: microsoft.public.windowsnt.protocol.tcpip (More info?)

The machines that need to keep an IP for all eternity should be set with
static addresses in a range outside of the DHCP server's range. Creating
reservations also works, but once a machine in permanently retired a new
machine can take that researved IP. Hope that helps.

-Drew