none
DHCP Problems in Server 2012 RRS feed

  • Question

  • Hello everyone,

    Please Help or Point me in a good direction!!!


    I am working with server 2012 DHCP . Under DHCP i have an ip address not a server name. ip  is 169.254.99.88 and host server not showing up ( This IP is Not In My Subnet and server is set to static ip 176.16.x.x)
    i have removed the dhcp roll and when  i go back and add the roll  the info comes back including the  scope that i have setup. all is green but it will not work
    I have pic but can not post them until they are able to verify your account.

    Links of pics

    http://i297.photobucket.com/albums/mm207/Dooane/server2012dhcp_zps78bb0de4.png

    http://i297.photobucket.com/albums/mm207/Dooane/server2012_zps4ac8b222.png

    Thanks

    Duane









    • Edited by MDP Roanoke Tuesday, October 23, 2012 1:21 PM
    Monday, October 22, 2012 4:14 PM

Answers

  • Okay, so the pictures you included in the original post are not related to your problem, because they show 192.168.1 addresses.

    If you wish to offer DHCP on the 176.16 network, only put one NIC on that network.  If you are not using the second NIC, disable it.  You do NOT want two NICs on the same subnet.

    Do not disable IPv6.  You are using it if you are running Windows Server 2012.

    It looks like, because you had two NICs, you ended up with the wrong one assigned to your DHCP service.  Disabling the one NIC and leaving the other NIC assigned to the 176.16 subnet should correct that.  DHCP can only work on the subnet for which it is defined.  If you had incorrectly ended up with it bound to the 169.254 address, it would never be able to offer addresses on 176.16.  See if disabling your unused NIC fixes the issue.  You might have to delete the scope and re-add it, but that should not be a big deal.


    tim

    Wednesday, October 24, 2012 3:53 PM
  • Tim

    After disabling Nic 2 and  resetting up DHCP serve is up and working.

    Also I recommend running BPA analyzer it help me fix some problems.

    Thanks

     Duane

    Monday, October 29, 2012 12:53 PM

All replies

  • I'm not clear on your explanations, but I will try to answer some things.

    "Under DHCP i have an ip address not a server name"  Not sure what you mean by this.

    "ip  is 169.254.99.88 and host server not showing up ( This IP is Not In My Subnet and server is set to static ip 176.16.x.x)"  Again, not sure what you mean.  I assume you are talking about a client machine that you want to receive an IP address.  The 169.254/16 address is what is known as an APIPA address.  It is an automatic assignment of a special range (169.254/16) for networks that do not have a DHCP available.  By default, all Windows NIC are initially configured for DHCP, and it they cannot find a DHCP server, they receive an APIPA address.  It allows two (or more) systems on the same network segment to communicate via IP without any additional configuration.  But, it is not something that you want to rely on in a managed network.  As for the fact that your server is set to 176.16/16, are you saying that is the address of the server you are trying to set up for DHCP, or the server that is showing the APIPA address is configured to have a 176.16/16 address?

    If you are saying that your DHCP server has a 176.16/16 address, and that is its only address, then you will have an issue with your DHCP configuration.  In your pictures, you show that you have defined your address pool for the 192.168.1/24 subnet.  The DHCP server needs to have a NIC on the subnet for which it is going to provide addresses.  If you want your host to be managed through the 176.16/16 address, you still need to have another NIC defined on the 192.168.1/24 subnet in order to be able to talk to machines requesting DHCP from that subnet.

    If I have misinterpretted your explanation, please correct me.


    tim

    Tuesday, October 23, 2012 3:25 PM
  • First I Would Like to thank you.

    No You have not misinterpreted my explanation.

    I will try to explain myself better.

    The Windows Server is a DHCP, DC file and Print Server. Sever has an IP of 176.16.10.6 I have set the Scope for the clients to be 176.16.10.15 – 172.16.10.254. with a  reservation of 176.16.10.6- 176.16.10.14 for printers and WSUS, when you look at DHCP the Server Icon is displaying the 169.254.99.88 address and not the Server Name IE win12, the Server has two nicks I only have one configured with an IP (IPV4). also in server 2008 r2 I have never had to configured two nicks to get DHCP to work. Is this something new you have to do in server 2012. It looks like the server is binding to the wrong nic is the possible?


    • Edited by MDP Roanoke Tuesday, October 23, 2012 5:50 PM
    Tuesday, October 23, 2012 5:49 PM
  • Hi,

    169.254.*.* is an APIPA adress and will be assigned to the computer if it can't reach the DHCP server. So, the problem is realated to the NIC not being able to communicate with the DHCP server.


    Blog: www.danielclasson.com/blog | LinkedIn: Daniel Classon | Twitter: @danielclasson

    Wednesday, October 24, 2012 8:45 AM
  • Thanks

    Should i disable one of the Nics. or configure them with static ips IE 176.16.10.6 and 176.16.10.7

    Nic 1 Has a static ip and Nic 2 is not set , i can get to the internet but no DHCP.

    the DHCP Server is showing APIPA address next to the Server Icon in DHCP


    Should i disable IPV6 i do not plan to use it.

    • Edited by MDP Roanoke Wednesday, October 24, 2012 12:31 PM
    Wednesday, October 24, 2012 12:11 PM
  • Okay, so the pictures you included in the original post are not related to your problem, because they show 192.168.1 addresses.

    If you wish to offer DHCP on the 176.16 network, only put one NIC on that network.  If you are not using the second NIC, disable it.  You do NOT want two NICs on the same subnet.

    Do not disable IPv6.  You are using it if you are running Windows Server 2012.

    It looks like, because you had two NICs, you ended up with the wrong one assigned to your DHCP service.  Disabling the one NIC and leaving the other NIC assigned to the 176.16 subnet should correct that.  DHCP can only work on the subnet for which it is defined.  If you had incorrectly ended up with it bound to the 169.254 address, it would never be able to offer addresses on 176.16.  See if disabling your unused NIC fixes the issue.  You might have to delete the scope and re-add it, but that should not be a big deal.


    tim

    Wednesday, October 24, 2012 3:53 PM
  • Tim

    After disabling Nic 2 and  resetting up DHCP serve is up and working.

    Also I recommend running BPA analyzer it help me fix some problems.

    Thanks

     Duane

    Monday, October 29, 2012 12:53 PM
  • Hi,

    Really it works, just restart the service after disabling the non usable nic.

    Thanks,

    SHUKRAS

    Wednesday, August 14, 2013 3:12 AM
  • Hello everyone,

    Please Help or Point me in a good direction!!!


    I am working with server 2012 DHCP . Under DHCP i have an ip address not a server name. ip  is 169.254.99.88 and host server not showing up ( This IP is Not In My Subnet and server is set to static ip 176.16.x.x)
    i have removed the dhcp roll and when  i go back and add the roll  the info comes back including the  scope that i have setup. all is green but it will not work
    I have pic but can not post them until they are able to verify your account.

    Links of pics

    http://i297.photobucket.com/albums/mm207/Dooane/server2012dhcp_zps78bb0de4.png

    http://i297.photobucket.com/albums/mm207/Dooane/server2012_zps4ac8b222.png

    Thanks

    Duane









    I have the same problem.

    I do have two NICs, WiFi and Ethernet.

    I am using both, with the server acting as a NAT between the wired NIC on 192.168.100.0/24 and the Wifi NIC on 10.221.232.0/22

    If I open DHCP using dhcpmgmt.msc, the server shows as the 169.254... address.

    If I open DHCP using the Server Manager console, it shows the server name.

    DHCP is functioning as expected. So it looks like this is a benign but annoying "feature"in Windows Server.


    G H


    • Edited by greenhart Tuesday, October 28, 2014 10:43 PM
    Tuesday, October 28, 2014 10:29 PM
  • gracias, he podido solucionar el problema , a parecer las NIC que no estaban siendo utilizadas estaban realizando conflicto, logré ver que en reverse lookup Zones estaban devolviendo este IP . 

    Logré solucionar este inconveniente descativando las NIC que no utilizaba, luego cerre la consola de DHCP y al abrirla nuevamente resolvía el nombre del Servidor. 


    Saludos.

    Friday, October 2, 2015 3:16 PM
  • I'm not clear on your explanations, but I will try to answer some things.

    "Under DHCP i have an ip address not a server name"  Not sure what you mean by this.

    "ip  is 169.254.99.88 and host server not showing up ( This IP is Not In My Subnet and server is set to static ip 176.16.x.x)"  Again, not sure what you mean.  I assume you are talking about a client machine that you want to receive an IP address.  The 169.254/16 address is what is known as an APIPA address.  It is an automatic assignment of a special range (169.254/16) for networks that do not have a DHCP available.  By default, all Windows NIC are initially configured for DHCP, and it they cannot find a DHCP server, they receive an APIPA address.  It allows two (or more) systems on the same network segment to communicate via IP without any additional configuration.  But, it is not something that you want to rely on in a managed network.  As for the fact that your server is set to 176.16/16, are you saying that is the address of the server you are trying to set up for DHCP, or the server that is showing the APIPA address is configured to have a 176.16/16 address?

    If you are saying that your DHCP server has a 176.16/16 address, and that is its only address, then you will have an issue with your DHCP configuration.  In your pictures, you show that you have defined your address pool for the 192.168.1/24 subnet.  The DHCP server needs to have a NIC on the subnet for which it is going to provide addresses.  If you want your host to be managed through the 176.16/16 address, you still need to have another NIC defined on the 192.168.1/24 subnet in order to be able to talk to machines requesting DHCP from that subnet.

    If I have misinterpretted your explanation, please correct me.


    tim

    Private IPv4 Ranges

    Class A (10.0.0.0 - 10.255.255.255 )

    Class B (172.16.0.0 - 172.255.255.255 )

    Class C ( 192.168.0.0 - 192.168.255.255 )

    Private IPv6 Ranges (uses Hex 0-9, A-F)

    yy=Prefix (first letter must have a F because 8th bit needs to have a 1 for local) exp FE

    Prefix Common types: FE=Site-Local  and FF=(never use because this is broadcast channel)

    gggggggggg=Global ID randomize to make it difficult to hack exp 7b9741953e

    ssss=subnet ID randomize to make it difficult to hack - exp 0a0a

    xxxx:xxxx:xxxx:xxxx= Your IP range you can use in a /64 subnet

    if you have a group of :0000:0000:0000:0000: you can shorten to :: but you can only use this once and the computer knows there are 8 octets so it will self fill the missing with the 0 in those spots

    leading 0s can be dropped

    put it together

    yygg:gggg:gggg:ssss:xxxx:xxxx:xxxx:xxxx/64

    it is that easy so example above

    fe7b:9741:953e:0a0a:0000:0000:0000:001d/64

    sort version

    fe7b:9741:953e:a0a::1d/64


    Thursday, December 3, 2015 5:24 PM
  • 176.x.x.x is a external ip range. You should use the Private IP Range I specified above or you will have IP conflict with outside world if your on the internet.
    Thursday, December 3, 2015 5:29 PM
  • You have other network adapters on the server, that are not connected, disable them. Restart the server. It will be fine
    Tuesday, December 15, 2015 3:07 PM
  • You have other network adapters on the server, that are not connected, disable them. Restart the server. It will be fine
    Tuesday, December 15, 2015 3:08 PM
  • netsh int ip reset c /resetlog.txt

    and all is good.

    Wednesday, March 9, 2016 3:12 PM
  • I worked on this problem for a few hours and then fixed it by disabling my unused NIC's but I found several other fixes (including one from Amile above) which should work so I posted them http://www.urtech.ca/2016/06/solved-dhcp-server-shows-169-254-99-88/

    I hope this helps someone else!


    Ian Matthews www.urtech.ca www.commodore.ca

    Friday, June 10, 2016 7:52 PM