I am getting the below event in the event log. What does it mean and how can
I fix it?
Thanks
Regards
Event Type: Warning
Event Source: DhcpServer
Event Category: None
Event ID: 1020
Date: 27/12/2004
Time: 10:15:50
User: N/A
Computer: MyServer
Description:
Scope, 192.168.16.0, is 100 percent full with only 0 IP addresses remaining.
Regards
Matthias
"John" <Jo...@nospam.infovis.co.uk> schrieb im Newsbeitrag
news:eyFAzjA7...@TK2MSFTNGP15.phx.gbl...
Check you DHCP scope and see what size it is configured for. Your scope may
be setup really small, or you may have too wide a range of addresses
excluded from the scope. Also, shorten your lease time to 1 day. If you
need a client to keep an IP address longer than one day, consider a
reservation for that client only (you don't want to many of these to
manage).
If you have to make any major changes to your scope, consider a setup that
makes sense to you. On small networks, I normally set aside 192.168.x.1 -
.10 for routers and such, 192.168.x.11 - .30 for servers and dedicated
hardware, 192.168.x.31 - .40 for printers, and 192.168.100 and up for
workstations. This has worked well on SBS networks as it is not possible to
run out of addresses without exceeding SBS limits and it's easy to manage
the static IP addresses with each 'group' having a specified range.
-TK
M/T Box Computers
How is your scope configured??
"John" <Jo...@nospam.infovis.co.uk> schrieb im Newsbeitrag
news:ucy5TgS7...@TK2MSFTNGP11.phx.gbl...
> Hi
>
> For some reason all the available ips were assigned. Attached is what is
> under 'Address Leases' in dhcp. What does it mean? Is it an attempt to
> hack?
> Is there a way to force the release of all leases?
>
> Thanks
>
> Regards
>
> "Matthias Eisner" <tw03...@technikum-wien.at> wrote in message
> news:uw8nBFB7...@TK2MSFTNGP15.phx.gbl...
You can force the IP address to be released by turning off your
workstations, then going through the DHCP management console right click
each IP lease you don't want and select 'delete'. Again, I think you should
look at your scope setup. With what you posted you should not be out of IP
addresses (even if you had 75 legitimate computers on your SBS network).
Check into this.
-TK
M/T Box Computers
This just shows the scope range. There is much more to it, like are there
any exclusions, etc. Also, you should have over 100 available IP addresses
even with the range given. How many machines are on your network? Are
there errors in the event logs concerning DHCP? If so, what are those
errors? You may want to Google on how to setup a DHCP scope using SBS.
It's fairly straight-forward and may help you resolve the issues you have
going on.
-TK
M/T Box Computers
If you have your clients on static IP (why??), what are you using DHCP for?
If you have enabled RRAS, it will take 10 IP's by default.
--
Regards,
Marina
Microsoft SBS-MVP
One of the Magical M&M's
"John" <Jo...@nospam.infovis.co.uk> schreef in bericht
news:e7ap$du7EH...@TK2MSFTNGP14.phx.gbl...
> Hi
>
> Ips 192.168.16.1-9 are excluded as per attached image. There are around 20
> pcs in the network but all are supposed to have fixed ips in the range
> 192.168.16.3-140. That is why it is bit confusing why so many ips are
being
> issued by dhcp. The dhcp setup was done during sbs setup and it worked
fine
> for a long time. There are no errors in the log for dhcp at present
although
> there was a warning earlier that dhcp scope is full prompting me to look
> into this.
>
> Thanks
>
> Regards
>
>
> "MTBoxTech" <te...@removethis.mtboxcomputers.com> wrote in message
> news:%23eU%23G6r7E...@TK2MSFTNGP10.phx.gbl...
What you are experiencing (the leases being eaten up) is a known bug in the
SBS DHCP server. Me and one other fellow were trying to figure it out, and
last I heard he was still waiting to hear back from MS on this (it's been a
couple/few months now). They had confirmed the bug and escalated it to the
programmers, but I don't think we've heard back yet on a patch or hotfix.
If you notice, the "Names" for the clients are the IP addresses that it's
trying to assign instead of an actual computer name. Another thing you may
notice is that the "Unique ID" is crazy. It's supposed to be the MAC
address of the NIC on the other end but what it shows for those erroneous
entries is actually the same IP string again shown as a hexadecimal
representation of it's ASCII value. i.e.:
For IP Address 192.168.16.141 the Client Name is also "192.168.16.141" and
the Unique ID is "3139322e3136382e31362..."
Hex 31 = Decimal 49; ASCII 49 = "1"
Hex 39 = Decimal 57; ASCII 57 = "9"
Hex 32 = Decimal 50; ASCII 50 = "2"
Hex 2E = Decimal 46; ASCII 46 = "."
Hex 31 = Decimal 49; ASCII 49 = "1"
Hex 36 = Decimal 54; ASCII 54 = "6"
Hex 38 = Decimal 56; ASCII 56 = "8"
.
.
.
etc.
A lot of the time it won't show all the erroneous entries in the DHCP
manager. You can 'fix' it by right-clicking the scope in the DHCP manager
and pick "Reconcile", then hit "Verify" and it will make a list of all the
ones it's not showing.
Adjusting lease time doesn't seem to make any difference.
After doing this they will show in the "Address Leases" list. From there I
just sort by Name to group all the IP "named" leases, then highlight and
delete them manually. It sucks and I find our server eats about 10
addresses a month or more.
It's bizarre, but they know about it; my advice is to call MS and tell them
that you have this problem and that you read here that it has been reported
previously. At the time MS said that they only had about 8-10 reports of it
so far and it only seems to be SBS users.
Come back and let us know what they tell you :)
Julio
--
-
"John" <Jo...@nospam.infovis.co.uk> wrote in message
news:e7ap$du7EH...@TK2MSFTNGP14.phx.gbl...
> Hi
>
> Ips 192.168.16.1-9 are excluded as per attached image. There are around 20
> pcs in the network but all are supposed to have fixed ips in the range
> 192.168.16.3-140. That is why it is bit confusing why so many ips are
being
> issued by dhcp. The dhcp setup was done during sbs setup and it worked
fine
> for a long time. There are no errors in the log for dhcp at present
although
> there was a warning earlier that dhcp scope is full prompting me to look
> into this.
>
> Thanks
>
> Regards
>
>
> "MTBoxTech" <te...@removethis.mtboxcomputers.com> wrote in message
> news:%23eU%23G6r7E...@TK2MSFTNGP10.phx.gbl...