?
Solved

DHCP not handing out addresses

Posted on 2008-10-22
10
Medium Priority
?
543 Views
Last Modified: 2012-05-05
Users are not getting IP addresses through DHCP.  Our small company has the DHCP server with 1 scope set up on a file/print server.  We've installed DHCP server on the DC and are ready to half the scope and put 1 half on the DC.  We also have collision detection set up on both DHCP servers.  Any other ideas or thoughts on solving this issue?
0
Comment
Question by:DDJCap
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
10 Comments
 
LVL 71

Expert Comment

by:Chris Dent
ID: 22777845

Is the DHCP server authorised? In the DHCP console, right click on the "DHCP" level and select Manage Authorised Servers.

Chris
0
 

Author Comment

by:DDJCap
ID: 22777886
The file/print server was and is authorized.  Once we split the scope into 2 and put half on the DC we'll authorize the DC as well.  DNS is also running on both servers.  We are not running WINS
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 22777927

Is the file and print server handing out addresses correctly at the moment? Authorisation is required before the server will begin serving clients.

All of this happens before DNS, or WINS, or really anything else gets a hand in. The client will send a broadcast for an address, it's simply up to the DHCP server to respond. If multiple servers are configured then both will respond, the client will use the first reponse it receives.

Chris
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 

Author Comment

by:DDJCap
ID: 22777970
The DHCP scope is set, the server authorized, and DHCP Server service runs automatically.  When users reboot, they are getting 169.254.....IP addresses.   How do we otherwise KNOW/TEST if the file/print server is handing out addresses correctly?  
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 22778021

You'd have to monitor network traffic. I'd expect it to throw errors in the Event Log if it's not behaving itself though.

It would be wise to double check the scope, including subnet mask and other items.

Chris
0
 

Author Comment

by:DDJCap
ID: 22778741
I checked the system logs under Event Viewer.  I have "The DHCP service encountered the following error while cleaning up the database:  %1"  According to MS, either the path to the DHCP server DB is gone or it's corrupt.

I verified the path led to dhcp.mdb, so I stopped DHCP, ran  jetpack dhcp.mdb tmp.mdb reconcile, then restarted DHCP services.  
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 22779526

Great, is it still failing to respond or did that catch it?

Chris
0
 

Author Comment

by:DDJCap
ID: 22780211
I've tried it out on 1 PC so far.  I logged into it locally for a video conference, then released and renewed the IP address.  No luck.  Tomorrow morning, I'll try it again on other PCs and see if this works.
If not, you'll be hearing from me.  Thanks to all who've lent their expertise so far.
0
 

Author Comment

by:DDJCap
ID: 22831683
After running the jetpack on the DHCP server DB, I set my PC to DHCP and rebooted.  No luck.
I deactivated the DHCP scope and unauthorized the DHCP server.  On the DC, I replicated the scope with all exemptions and reservations.  I then activated the scope and authorized the DHCP server.  I changed my PC configuration to DHCP and rebooted.  Even though my PC was one of the reservations, I still did not get an IP address.  
I have verified teh DHCP server(s) have a static IP address, both have DNS entries, both can be pinged via IP and name, have stopped and restarted DHCP services, and checked scope options
0
 

Accepted Solution

by:
DDJCap earned 0 total points
ID: 22876483
We have a solution:   The Network Threat detection from Symantec Endpoint 11.
Once we disabled it on the DC, all was kosher.
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums. I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
Occasionally you run into the website or two that will not resolve properly using your own DNS servers.  Some people simply set up global forwarders for their DNS server.  I don’t recommend doing this because it can cause problems resolving addresse…
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…
Suggested Courses
Course of the Month8 days, 14 hours left to enroll

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question