Advertisement

02.26.2008 at 12:16PM PST, ID: 23194925
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

Phantom MACs in DHCP causing BAD_ADDRESS leases

Tags: Microsoft, Windows Server, 2003, DHCP
Earlier today, an end user called in an autoenrollment error.  Taking a look at the DHCP applet revealed that autoenrollment failed because the scope was full (not normal, as the scope is 155 addresses and there are only ~80 clients).  A look at the address leases showed 76 BAD_ADDRESS entries.  There are a couple of strange properties of these entries:

1)  The MAC addresses are incomplete - they aren't the normal 12 characters.  Instead, they're 8 characters long, for example:  3fc909c0.  
2)  The leases expire in 1 hour, which is not the setting, either for the server or the scope (the settings for both are 8 days)
3)  The MAC addresses are sequential, for example f0c909c0, f1c909c0, f2c909c0, f3c909c0, etc.

If the BAD_ADDRESS entries are deleted, they begin to re-appear at the rate of 1 every 2 seconds until the scope is full.

There are no warning or error messages in the server's event logs, and the DHCP log only shows the conflicts that arise when legit client machines attempt to renew addresses but there are no entries that show the phantom addresses making the requests... see below:

10,02/26/08,15:08:29,Assign,192.168.201.220,computername.domainname.com,001372CB3BDD,
13,02/26/08,15:08:29,Conflict,192.168.201.220,BAD_ADDRESS,,

Any help would be appreciated!
Start your free trial to view this solution
Question Stats
Zone: Networking
Question Asked By: seacon
Solution Provided By: tech_tonic
Participating Experts: 1
Solution Grade: B
Views: 9
Translate:
Loading Advertisement...
02.26.2008 at 04:58PM PST, ID: 20990490

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
02.26.2008 at 04:59PM PST, ID: 20990503

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
02.27.2008 at 05:57AM PST, ID: 20993938

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
Loading Advertisement...
20080236-EE-VQP-29 / EE_QW_2_20070628