DHCP on SBS 2003 - BAD_ADDRESS in DHCP lease list

As per recommended by this group, I finally had the time between other
projects to move the DHCP to the SBS, instead of leaving it up to the
router.

I set the scope to 192.168.0.110 to 220, where the router had it 100 to
190. This was done to rectify the issue with the server being locked at 100
(because it's easier to remember when going in on remote).

Immediately after the new scope got activated, I have an entry in the lease
list as follows:

192.168.0.120 BAD_ADDRESS 7800a8c0
"This address is already in use"

Obviously, this MAC is 4 characters short of being valid. But what does
that mean? I don't have any entries on the router snapshot before I
deactivated its DHCP that matches this...

Also, after activating the server DHCP, one terminal - only one - came up
with the IP conflict message. Only the IP it had assigned wasn't in use.
Release/renew didn't work ("Invalid Directory"), but the XP Repair
Connection got it re-established.
--
Rene Brehmer
IT Technician

North Hill Inn
http://www.northhillinn.com

If you look in DHCP Server to see what has that addreess

you could also go to each workstation and do an ipconfig /release all to clear old leases and then do an ipconfig /renew

--
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"Rene Brehmer" <rene@metalbunny.net> wrote in message news:1mmyjyxprjnww$.1q8uabfjtjmqy.dlg@40tude.net...
As per recommended by this group, I finally had the time between other
projects to move the DHCP to the SBS, instead of leaving it up to the
router.

I set the scope to 192.168.0.110 to 220, where the router had it 100 to
190. This was done to rectify the issue with the server being locked at 100
(because it's easier to remember when going in on remote).

Immediately after the new scope got activated, I have an entry in the lease
list as follows:

192.168.0.120 BAD_ADDRESS 7800a8c0
"This address is already in use"

Obviously, this MAC is 4 characters short of being valid. But what does
that mean? I don't have any entries on the router snapshot before I
deactivated its DHCP that matches this...

Also, after activating the server DHCP, one terminal - only one - came up
with the IP conflict message. Only the IP it had assigned wasn't in use.
Release/renew didn't work ("Invalid Directory"), but the XP Repair
Connection got it re-established.
--
Rene Brehmer
IT Technician

North Hill Inn
http://www.northhillinn.com

On Mon, 25 Feb 2008 15:49:58 -0600, Cris Hanna [SBS-MVP] wrote:

> If you look in DHCP Server to see what has that addreess
>
> you could also go to each workstation and do an ipconfig /release all to clear old leases and then do an ipconfig /renew

Well, that was the thing, I couldn't find anything that matched that messed
up MAC. Today however, the BAD_ADDRESS entry is no longer there.

So I am still clueless as to what caused it. I haven't figured out how to
access the DHCP log yet, but atleast now the DHCP appears to work.

Rene Brehmer wrote:
> On Mon, 25 Feb 2008 15:49:58 -0600, Cris Hanna [SBS-MVP] wrote:
>
>> If you look in DHCP Server to see what has that addreess
>>
>> you could also go to each workstation and do an ipconfig /release
>> all to clear old leases and then do an ipconfig /renew
>
> Well, that was the thing, I couldn't find anything that matched that
> messed up MAC. Today however, the BAD_ADDRESS entry is no longer
> there.
>
> So I am still clueless as to what caused it. I haven't figured out
> how to access the DHCP log yet, but atleast now the DHCP appears to
> work.

SBS DHCP leased .120 and another client had this leased from the router and
it was still valid. This should only happen durring transistion periods
where scopes overlap. You can also configure 'conflict detections", but you
shouldn't really need it in the future if you stay on the right path.


--
/kj