DHCP not handing out addresses

Hi all
I have Windows Server 2008 sp2 roles AD DNS and DHCP.
Several days my server DHCP is "hangs"
a few hours after restart
C:\Windows\system32\svchost.exe -k DHCPServer run on 50 % on procesor and mmc not responding I must before kill proses svchost and start DHCP is
looks good but not response to client PC

Run a free malware scan using the following to make sure there is no infection.
Microsoft's Safety Scanner (gest updated regularly):
http://www.microsoft.com/security/scanner/en-us/default.aspx
MalwareBytes free scanner - update before you run (to use the free version for occasional scans, do not opt to try the free 30 day pro version during installation)
www.malwarebytes.com
Are there any event log errors?
As a test, if you run it without any third party services running, does it do the same thing? To do that, from a Start/Run box, run
msconfig, select Service tab, click on Hide Microsoft Services, then make sure the list left is checked, and disable them, and restart. Run it as a test, and if it doesn't occur, then you know it's third party software doing it.
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Similar Messages

DHCP not handing out IP leases to non-domain members

Recently gotten DHCP working, server gives out IP address for domain computers only, non-domain computers do not get a lease and if I manually assign an IP and the device will gain network and internet access. I used the wizard to create the DHCP IP range
but have not done much beyond that. I have setup DHCP servers using Linux, my first go around with Windows. Any further information you may need please let me know.
Thanks.

Alright here we go, took some digging but found the solution for all issues.
netsh int ip reset
netsh winsock reset
Just as further step I restarted DHCP on the server, one more time, then restarted the network interface on my test laptop, I was given an IP address from the server and could browse the network\internet. This morning I checked Address Lease's and now
I see ten address have been leased for RRAS and all devices I have ran the above command on are pulling an address. So the solution to my problem, disable filters for allowed devices in DHCP manager, increase the range or block of IP address to be leased and
finally rebuild\reset winsock and ip stack on domain devices.
Hope this helps someone else in the future.
Cheers!

New Subnet not handing out IP Addresses

I have created a new subnet (10.168.64.x) on a Netware 6.5 server using DNS/DHCP Admin Tool.
The old subnet (10.168.60.x) is running out of IP addresses but still functioning properly. The new subnet (10.168.64.0) is showing in DNS/DHCP but not handing out addresses.
I have done all of the following-
-Bound an IP address to the Server in the range of the new subnet (10.168.64.1)
-Unloaded and Loaded DHCPSRVR
Still no luck - What are some other steps I can take to get this new Subnet to hand out IP's?
I loaded DHCPSRVR -d2 and got the following message - https://docs.google.com/document/d/1...it?usp=sharing
Any help is appreciated!

If you don't get any replies here, try the DNS/DHCP specialist forum
https://forums.novell.com/novell-pro...dent/dns-dhcp/

Lion Server not handing out DHCP addresses to Snow Leopard client

I have been pulling my hair out over this.
Here is the layout
Lion Server running on the newest Mac Mini and doing mail, DNS, DHCP, Software update and has a valid, not self assigned, certificate
3 clients running Lion Desktop (2 iMACs and a MBP pro (all no more that a year old and all woth the current updates)
1 client running Snow Leopard Desktop (last years 13 inch MBA)
The 3 Lion clients can get dhcp fro mthe Lion server without any issue
The SL client cannot get a DHCP address from the Lion server
A tcpdump shows the DHCP request coming from the MAC address of the SL client but no response from the Lion Server and nothing showing a deny in the logs for the DHCP server or any other system/kernel logs. The Lion clients all show the request and reply for them. All 4 clients currently have a static assignment in DHCP but even if I remove them all and do auto-assign for everything or even each one individually, the SL client will not get an address both on the Wifi and Ethernet (I have the USB ethernet adapter).
I also have an Aiport Extreme and if I use that for the DHCP server then all clients get the addresses. I know the DHCP server in the extreme cannot be shut down but if you give the extreme a static address then assign dhcp on the extreme to only give out one address and that is the same one that is statically assigned then it "thinks" it is out of addresses and no longer tries to assign addresses
At first I thought there was a conflict between the extreme and the Lion server but as I mentioned above, tcpdump clearly shows the requests going right to the Lion server
I'm usually pretty good at this kind of thing but this one has me stumped. I'm thinking bug, anyone else run into this yet?

Ryan jones,
> Having trouble with our dhcp server handing out IP addresses through the
> Wireless Lan Controller.
Has it ever worked? Is the Wireless controller configured to forward DHCP
requests to your DHCP server?
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)
Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

AX does not hand out ip addresses in roaming mode

I am trying to set up roaming network in my house using a Airport Extreme as the main router and a ethernet connected (via Powerline HD) Airport Express on the second floor of my house. I followed the usual instructions to set up the Airport Express to create wireless network in bridge mode. The Express allows clients to connect and accepts the password but does not hand out ip addresses. so the roaming device (an ipad and an Air) end up with self-assigned addresses in the 169.*.*.* range.
How do I correct this?
option click on the Air wifi symbol shows that its corrected to the correct wifi base station
Airport Utility sees both the main Extreme base station and the Express second floor base station, and neither reports any problems.
Thanks.

I am trying to set up roaming network in my house using a Airport Extreme as the main router and a ethernet connected (via Powerline HD) Airport Express on the second floor of my house. I followed the usual instructions to set up the Airport Express to create wireless network in bridge mode. The Express allows clients to connect and accepts the password but does not hand out ip addresses.
Actually, with the AirPort Express in bridge mode, the AirPort Extreme would be the router "handing out" the IP addresses as they would just be "passing through" the Express in this configuration.
Let's double-check your roaming network configuration, just to be sure nothing was missed.
Roaming Network Setup
Ref: See page 42 of the Apple AirPort Networks guide.
Setup the AirPort connected to the Internet to "Share a public IP address." Internet > Internet Connection > Connection Sharing: Share a public IP address
Setup the remaining AirPorts, as bridges. Internet > Internet Connection > Connection Sharing: Off (Bridge Mode) For each AEBSn in the roaming network:
For each base station:
Connect to the same subnet of the Ethernet network.
Provide a unique Base Station Name.
The Network Name (SSID) should be identical.
If using security, use the same security type (WEP, WPA, etc.) and password. Note: It is highly recommended that you use WPA2 Personal for best bandwidth performance.
Make sure that the channel is set at least three channels apart from the next base station to prevent Wi-Fi interference.

DHCP still giving out addresses to clients on the Deny filter

My DHCP server is handing out addresses to clients that I have put on the deny list. The "Enable Deny List" is checked. Its not to every client either. It is just a handful that keeps popping back. What am I missing?

Hi Alphateam,
Have you confirmed that the deny is on all interfaces, wired and wireless of said machines.

Server 2008 DHCP is handing out the wrong DNS server.

We have two new 2008 DC that handles, DNS, DHCP and WINS. Our DHCP scopes have been migrated to these servers. We are seeing some random issues where clients are using the new dhcp server but the old dns server information is listed for the some systems. We discover this by using network monitor on the old DC, DNS, DHCP server. Once the client performs a ipconfig /renew, the problem is corrected. Any ideas?

Hi BrianAuH20,
Thank you for posting here.
Based on your description, I understand that your Windows 2008 DHCP server hands out the wrong DNS server address.
To troubleshoot this issue, please perform the follow steps to see whether the clients retrieve the right DNS server address.
1.     Temporarily make the old DC, DNS, DHCP server offline.
2.     Check the new 2008 DHCP server setting.
                      i.        In the DHCP console tree, under Scope [172.16.0.0] SS Scope, right-click Scope Options, and then click Configure Options.
                     ii.        On the Advanced tab, verify that Default User Class is selected next to User class.
                    iii.        Select the 006 DNS Servers check box, in IP Address, under Data entry, type DNS Server IP address, and then click Add.
                    iv.        Select the 015 DNS Domain Name check box, in String value, under Data entry, type your domain's FQDN name, and then click OK.
3.     Restart the DHCP service.
For more information, you may refer to:
http://technet.microsoft.com/en-us/library/ee404786(WS.10).aspx
Hope this helps.
Sincerely,
Wilson Jia
This posting is provided "AS IS" with no warranties, and confers no rights.

New 2008 R2 DHCP server will not hand out IP addresses

We've recently migrated our Domain Controllers to 2008 R2, Virtual Machines. (DC3 & DC4).
DC2 is an older 2003 box, 32 bit, set for retirement. All former roles have been moved to DC3 & DC4, including FMSO roles, and the server (DC2) has been demoted. The only service that remains on DC2 is DHCP.
I've used NETSH to export / import the DHCP info to DC4. All reservations have transferred ( Printers) and the scope shows "active" on DC4 and authorized, and running, but whenever I shut DHCP down on DC2, DC4 doesn't start handing out
IP addresses to clients.
Even after rebooting a client multiple times, running ipconfig /release & /renew, it never finds the new DHCP server, nor does the server show any client information in the address leases. (other than reserves)
We have a Cisco ASDM deployed, but DHCP and DNS are both disabled on this device, so I'm not sure IP Helper would be an issue here.
Since both my new DC's are 2008R2, do I need to elevate active directory up to 2008 function before DHCP will work?

Hi,
Is the issue resolved? As suggested by
Wyatt Miller, you can check if it was caused by IP helper.
In addition, is the new server authorized?
Here is a migration guide for you:
Migration of DHCP Server from Windows Server 2003 to Windows Server 2008
http://blogs.technet.com/b/teamdhcp/archive/2009/02/18/migration-of-dhcp-server-from-windows-server-2003-to-windows-server-2008.aspx
Hope this helps.

DHCP not delivering IP addresses

I had DHCP enable and everything working great. After a manual reboot of the system, DHCP is not delivering IP address to the clients.
If I insert the values manually, everything works.
Any ideas?

Ater restarting everything works... :s

WRE54g not handing out IP address to client systems

This is probably a silly question, but I'll ask it anyways.
We have a Linksys WRT54G ver6 running latest firmware revision 1.02.0 along with a WRE54G ver3 running firmware 3.01.01.
Both devices are configured to use WPA-PSK security, and I have reconfirmed that the key is the same on both devices.
The wireless router is connected to our existing wired network, and so the DHCP functionality of the router is disabled as we want wireless clients to get their IP address from our existing DHCP server on the wired network. This part works fine, wireless systems can connect to the wireless router and they are given an IP address from the range configured on our wired DHCP server.
The range expander has been configured with the same SSID, and security settings as the wireless router. Wireless clients can see the SSID being broadcast by the range expander and they are able to connect to it, but they are not given an IP address.
Is this because the range expander is expecting to receive the IP's from the DHCP server on the wireless router ( which is disabled ) and does not know anything about our existing wired DHCP server?
Thanks.

ok I knew this was going to be something silly.
I tried disabling the wireless security on both devices and this allowed wireless clients to receive an IP address from the Range expander ( verified by the MAC address of the Access point the wireless clients were connected to ).
So I rechecked the security settings again, the key was fine but the issue turned out to be that the wireless router was configured to use WPA2 while the range expander only seems to have support for WPA. Once I enabled WPA on the wireless router, the wireless clients were able to connect and receive their IP address via the Range expander.

WRVS4400N : DHCP not assigning IP addresses if WAN link is down

Hello,
With the latest firmware installed (the one suporting fixed IP based on MAC), I have one problem: the DHCP server is not assigning addresses when the WAN link is down. When it is up, it generally assign IP based on the configuration binding (MAC/IP). But it sometimes fail to do so. Before using the wrvs4400n I had no issues with DHCP wrt54G and other routers.
Any hints ?
Thanks.
V.

Hi there!
Thanks for contacting the business support - other guys got the same problem.
I'm now back on firmware version 1.00.16 and everything works fine.
But the new features were nice to have!

DHCP not giving out adresses

Hi there,
just upgraded from Lion Server to ML Server. I found that everything is runnign quite smooth here (OD Master with 800+ users, NetInstall, etc etc), but I have problems with my DHCP Service:
As is written in Apple's KB Article, all the config files with my setup from Lion Server are still there and the service also is up and running, but my clients just won't get IPs and settings via DHCP. I also thought about firewall issues, but just as with DHCP, these settings were kept and are up and running. I've also found the tutorial from Krypted.com and read the other posts, but I really can't find the problem's source.
Anybody here with similar problems?
best whishes,
Christian

Thanks man! That's been it. Who would guess, that although they transfer all the settings when upgrading, the server is disabled

WRTU54G-TM Port Forward issues, DHCP server disabled but still gives out addresses

I've seen other posts about port-forwarding issues. I've had to hard-reset the device twice in 2 months to clear this up.
One issue that I can't figure out at all is that the DHCP server gives out addresses when it is set to disabled. This is a problem because it gives out the public DNS servers, which will not resolve addresses on my LAN. Anyone else seen this?
Anyone had success putting this router behind a better one and still getting the phone SIM to register and work?

Have you tried to upgrade the firmware on your Router?
Click Download the latest firmware for your Router and save the Firmware file on your Desktop.
Once you Download the firmware for your Router, Now you need to login to the Router setup page and click on the "Administration" tab and below click on "Firmware Upgrade" and then click on the Browse Button and select the firmware file and click on Upgrade.
Once the firmware is upgraded successfully then you need to Reset your Router and Re-configure all the settings on your Router from scratch.

Dhcp not allocating addresses

My network is managed by Mac Mini Server (Lion) with an Airport Extreme.
I have the wireless set up as WPA2 Enterprise with the Radius Server, Open Directory, DNS and DHCP running on my Mac Mini Server.
In the past week, possibly since the last updates were applied, all wireless devices are having real issues connecting to the network. They are authenticating OK but an address is either never assigned or appears after 5 or ten minutes. To verify this I tried to connect iPad. This was set to use DHCP and the wifi symbol appears intermittently at the top of screen but on the networks page a spinning wheel appears next to the network name and the address details (i.e local address, router, DNS, etc.) are all empty. If I configure for manually entered address details the deveice connects immediately and works fine. Switching back to DHCP and the problem comes back (i.e. connects to wifi but no address is ever allocated).
Any ideas on why DHCP would suddenly stop working. I have tried restarting the service, rebooting the Airport, rebooting the server but nothing seams to fix it. Every thing was working just fine for the past 6 months.

Thanks for reply.
Router is:
Netopia ADSL Gateway 3346N-002
4 port 10/100 Ethernet built-in
The settings in the Control Panel didn't show anything of note.
What's interesting is that when the user's laptop went back to the hotel again today, the same issue cropped again -- hotel's DHCP not giving IP Address. The office DHCP server was assigning no problem.
Then... I checked Access Connections Profiles and noticed that "Disable this wireless radio when switching to a different location" was not checked for any profiles.
I checked off on all profile and then the hotel DHCP made the connection.
I did read somewhere that a possible fix is to do an IPCONFIG/RELEASE * and then do an immediate Shutdown/Restart. Issue is that I didn't have this option on the user's laptop before I made the Access Connections fix.
Please reply to clarify or add anything -- I appreciate your quick response because I spent 4 additional hours last night.
Paul

Handing out wrong default gateway

I'd like to add a WRT54g2 to my LAN. I'd like it to communicate with my existing LAN router, and not to talk directly to the LAN. Therefore, in Basic Setup, I don't have the top part (Internet Setup) configured. Is that a mistake?
But, it seems that when I enable DHCP, it hands out its own IP as gateway, and then doesn't seem to send the traffic on upstream. When I configure clients manually with the real router IP, they work fine.
So, I'd like, I guess, Linksys to forward traffic on a static route to real router. How do I do this? Adding a route to real router yields the error, "maybe default route already exists."
Thanks!

Only one router should have DHCP enabled, your first router is doing this. Connect the 2nd router via cable to Lan-Lan,disable DHCP and set it's IP to 192.168.2.1.

DHCP not handing out addresses

Similar Messages

Maybe you are looking for