Re: DHCP superscope only assigns addresses from one subscope

Why do you have two Scopes within a Superscope in the first place?


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"Marco Senft" <m.senft@xxxxxx> wrote in message
news:47a19e71$1_1@xxxxxxxxxxxxxxxxxxxxx
Hello all,

Since a couple of weeks I'm at loss with a Windows 2003 Server (Standard
Edition) with DHCP service enabled. I made a superscope containing two
subscopes. I'll refer to them as "first" and "second" scope.

When running, the DHCP server gives out leases from the first scope only,
until no more addresses are available in this subscope. The server then
begins giving out leases from the second subscope. In the Event Viewer,
every hour a log entry is created saying: "Scope, 192.168.1.0, is 100
percent full with only 0 IP addresses remaining."

Is it normal that the DHCP server gives out all leases from one subscope?
Shouldn't it give out leases from all scopes about equally? And why are
the system events occuring when in fact there's nothing to worry about?
I'd really like the server to give out leases from both subscopes equally
and especially avoiding the system events and the blue exclamation mark in
DHCP manager.

Thanks for your replies and hints.

Bye,
marco


--
Technische Treuhand GmbH Tel. +41 81 413 11 92
http://www.t2g.ch/ Mobile +41 79 696 16 25


.

Relevant Pages

  • DHCP superscope only assigns addresses from one subscope
    ... When running, the DHCP server gives out leases from the first scope only, until no more addresses are available in this subscope. ...
    (microsoft.public.windows.server.networking)
  • Re: DHCP request from nowhere
    ... Refreshing the view of active leases shows nothing; ... 31 = ascii 1 ... There is a RRAS server in the environment but IPs gathered by RAS show ... the client a DHCP address or relays its request to a DHCP server. ...
    (microsoft.public.windows.server.networking)
  • Re: VOP_LEASE
    ... for any read leases for the file). ... would certainly be useful for a hypothetical future NFSv4 server. ... NFS client with NQNFS would implement the VOP_LEASE ... and trap those accesses to manage the lease with the remote server. ...
    (freebsd-arch)
  • Re: VOP_LEASE
    ... for any read leases for the file). ... would certainly be useful for a hypothetical future NFSv4 server. ... VOP_LEASE is supposed to implemented by a filesystem client. ...
    (freebsd-arch)
  • Re: DHCP Migration
    ... You get the one configured the way you like but leave the scopes ... You would have a separate scope for each subnet. ... to the proper DHCP Server. ... configured and activated on the DHCP Server and the Router was forwarding ...
    (microsoft.public.windows.server.networking)