none
Several Windows 7 Enterprise x64 machines are not getting IP address RRS feed

  • Question

  • Hi

    The last month we have had many computers that is not getting an ip address. It happens on computers that has not been used for a while and on computers coming from another network like home network. We have had a rush of computers with this problem after the Christmas holidays.

    They are getting ip address 169.254.1.1 and the network responsible says that the computers are denying the ip address from the server and the error is on the local computer not on the server.

    This happens on different models, network cards, locations and on both Wlan and Lan. On the same computer Wlan can get an ip adresse and LAN is not or opposite. Our company is using the same image in other countries and they do not have this problem. The only difference is languagepacks and some GPO settings.

    The workaround is in some cases to release and then renew ip address, but in most cases we have to uninstall network driver and install it again. Update the driver is not working. Netsh int ip reset is not working.
    Have also tried hotfix KB2824546 and KB2459530.

    The problem is returning for some of the clients.

    Have logged the DHCP client, with this result:

    Level    Date and Time    Source    Event ID    Task Category
    Information    08.01.2016 09:14:16    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Warning    08.01.2016 09:14:16    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:14:13    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Information    08.01.2016 09:14:13    Microsoft-Windows-Dhcp-Client    50007    Protocol State Event    Discover-Offer-Request-Ack is initiated on the adapter with Interface Id 19
    Information    08.01.2016 09:09:38    Microsoft-Windows-Dhcp-Client    50018    Protocol State Event    Inform is sent in the adapter 12. Status code is 0x0
    Information    08.01.2016 09:09:35    Microsoft-Windows-Dhcp-Client    50018    Protocol State Event    Inform is sent in the adapter 12. Status code is 0x0
    Information    08.01.2016 09:09:30    Microsoft-Windows-Dhcp-Client    50063    Address Configuration State Event    Dhcp has notified NLA for the configuration changes for the interface 19
    Warning    08.01.2016 09:09:30    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:08:58    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Warning    08.01.2016 09:08:58    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:08:42    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Warning    08.01.2016 09:08:42    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:08:33    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Warning    08.01.2016 09:08:33    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:08:30    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Information    08.01.2016 09:08:30    Microsoft-Windows-Dhcp-Client    50020    Protocol State Event    Broadcast bit is toggled in the adapter 19. Broadcast bit after toggling is true
    Information    08.01.2016 09:08:30    Microsoft-Windows-Dhcp-Client    50063    Address Configuration State Event    Dhcp has notified NLA for the configuration changes for the interface 19
    Warning    08.01.2016 09:08:30    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:07:59    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Warning    08.01.2016 09:07:59    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:07:43    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Warning    08.01.2016 09:07:43    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:07:38    Microsoft-Windows-Dhcp-Client    50018    Protocol State Event    Inform is sent in the adapter 12. Status code is 0x0
    Information    08.01.2016 09:07:35    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Warning    08.01.2016 09:07:35    Microsoft-Windows-Dhcp-Client    50023    Protocol State Event    Offer Receive Timeout has happened in the Interface Id 19
    Information    08.01.2016 09:07:35    Microsoft-Windows-Dhcp-Client    50018    Protocol State Event    Inform is sent in the adapter 12. Status code is 0x0
    Information    08.01.2016 09:07:35    Microsoft-Windows-Dhcp-Client    50058    Address Configuration State Event    Your computer was successfully assigned an address from the network, and it can now connect to other computers.
    Information    08.01.2016 09:07:35    Microsoft-Windows-Dhcp-Client    50042    DNS State Event    Dns registration has happened for the adapter 12. Status Code is 0x0. DNS Flag settings is 0.
    Information    08.01.2016 09:07:35    Microsoft-Windows-Dhcp-Client    50028    Address Configuration State Event    Address 169.254.1.136 is plumbed to the adapter 12. Status code is 0x0
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 19.Status code is 0x0
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    50007    Protocol State Event    Discover-Offer-Request-Ack is initiated on the adapter with Interface Id 19
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    60018    Media State Event    PERFTRACK (DHCPv4): Media Connect on adapter 19
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    60019    Media State Event    PERFTRACK (DHCPv4): End of Media Connect on adapter 19
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    50025    Protocol State Event    Cancelling pending renewals on the adapter in the Interface Id 19
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    50033    Media State Event    An interface is added whose interface index is 19 and Status Code is 0x0.
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    50004    Address Configuration State Event    Dhcp is enabled on the adapter with Interface Id 19
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    50001    Media State Event    Media Connect notification received with Interface Id 19
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    50025    Protocol State Event    Cancelling pending renewals on the adapter in the Interface Id 16
    Information    08.01.2016 09:07:32    Microsoft-Windows-Dhcp-Client    50002    Media State Event    Media Disconnect notification received with Interface Id 16
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50063    Address Configuration State Event    Dhcp has notified NLA for the configuration changes for the interface 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50035    Address Configuration State Event    Routes are updated in the adapter 12. Status Code is 0x0
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50059    Address Configuration State Event    Route is added with the values Dest = 0.0.0.0, DestMask = 0.0.0.0, NextHop = 169.254.1.1, Address = 169.254.1.136
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    60001    Protocol State Event    PERFTRACK (DORA): Offer is accepted in the adapter 12.Offered Address is 169.254.1.136.Server address is 169.254.1.1
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    60011    Protocol State Event    PERFTRACK (DORA): Offer is accepted in the adapter 12.Offered Address is 169.254.1.136.Server address is 169.254.1.1
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50013    Protocol State Event    Ack is accepted in the adapter 12. Received Address is 169.254.1.136.Server address is 169.254.1.1
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50012    Protocol State Event    Request is sent from the adapter 12. Status code is 0x0
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50010    Protocol State Event    Offer is accepted in the adapter 12.Offered Address is 169.254.1.136.Server address is 169.254.1.1
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50009    Protocol State Event    Discover is sent from the adapter 12.Status code is 0x0
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50007    Protocol State Event    Discover-Offer-Request-Ack is initiated on the adapter with Interface Id 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50063    Address Configuration State Event    Dhcp has notified NLA for the configuration changes for the interface 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50060    Address Configuration State Event    Route is deleted with the values Dest = 0.0.0.0, DestMask = 0.0.0.0, NextHop = 169.254.1.1, Address = 0.0.0.0
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50012    Protocol State Event    Request is sent from the adapter 12. Status code is 0x0
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50006    Protocol State Event    Request-Ack is initiated on the adapter with Interface Id 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    60018    Media State Event    PERFTRACK (DHCPv4): Media Connect on adapter 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    60019    Media State Event    PERFTRACK (DHCPv4): End of Media Connect on adapter 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50025    Protocol State Event    Cancelling pending renewals on the adapter in the Interface Id 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50033    Media State Event    An interface is added whose interface index is 12 and Status Code is 0x0.
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50004    Address Configuration State Event    Dhcp is enabled on the adapter with Interface Id 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50001    Media State Event    Media Connect notification received with Interface Id 12
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    60003    Address Configuration State Event    PERFTRACK: DHCP not enabled in the adapter 16
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    60013    Address Configuration State Event    PERFTRACK: DHCP not enabled in the adapter 16
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    60018    Media State Event    PERFTRACK (DHCPv4): Media Connect on adapter 16
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    60019    Media State Event    PERFTRACK (DHCPv4): End of Media Connect on adapter 16
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50025    Protocol State Event    Cancelling pending renewals on the adapter in the Interface Id 16
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50033    Media State Event    An interface is added whose interface index is 16 and Status Code is 0x0.
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50005    Address Configuration State Event    Dhcp is disabled on the adapter with Interface Id 16
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50001    Media State Event    Media Connect notification received with Interface Id 16
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50002    Media State Event    Media Disconnect notification received with Interface Id 13
    Information    08.01.2016 09:07:31    Microsoft-Windows-Dhcp-Client    50001    Media State Event    Media Connect notification received with Interface Id 1
    Information    08.01.2016 09:07:09    Microsoft-Windows-Dhcp-Client    50025    Protocol State Event    Cancelling pending renewals on the adapter in the Interface Id 12
    Information    08.01.2016 09:07:09    Microsoft-Windows-Dhcp-Client    50025    Protocol State Event    Cancelling pending renewals on the adapter in the Interface Id 19

    Any suggestions on what to do now?

    Friday, January 8, 2016 9:00 AM

Answers

  • Hi MR.Fieldwood,

    Thank you for your reply.

    Actually, capturing packages by Wireshark has no relationship with DHCP. Please check the schedule task since you suppose something triggered it.

    We would like to suggest you start the Windows in clean boot mode due to we would also consider if any 3rd party software block it.

    https://support.microsoft.com/en-us/kb/929135

    Wish you have a nice day.

    Best Regards

    Simon


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, January 13, 2016 1:21 AM
    Moderator

All replies

  • Just curious: Are all of these problem computers at the same location? Were any switches/routers changed recently?


    Ha®®y

    Friday, January 8, 2016 3:17 PM
  • Different locations. Switches/routers not changed.
    Monday, January 11, 2016 6:49 AM
  • Hi MR. Fieldwood,

    I have read your issue. Since you have found a workaround to solve it, uninstall the driver helps the client work fine, you could try deploy the drive again to install.

    https://technet.microsoft.com/en-us/library/hh831764.aspx?f=255&MSPPError=-2147217396

    We suppose there are three possibility of the issue.

    1. When client failed to send query for DHCP server.

    2. DHCP server does not received the query or discard the query.

    3. Client does not received the ACK from DHCP sever, or the client discard it due to the driver in client make the client consider it is a invalid ACK.

    You need to capture network packages to find the exact reasons.

    Good luck to fix it.

    Best Regards,

    Simon 


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, January 11, 2016 7:15 AM
    Moderator
  • I'm experiencing roughly the same issue.

    I've ruled out possibilities 1 and 2.

    I have wire shark running (for possibility 3), but no error was ever shown.

    This I saw this...

    https://social.technet.microsoft.com/Forums/en-US/c1c73ab0-1915-4165-a3bd-1746329ab7b9/dhcp-traffic-blocked

    Monday, January 11, 2016 6:06 PM
  • In my case it is not the firewall. Have turned it off.

    The strange thing is that when I am running Wireshark the computer suddenly gets an ip address. That happened on my previous test computer too, not Wireshark, but while I was checking logs. Looks like logging in with local admin account triggers something.

    Tuesday, January 12, 2016 10:08 AM
  • Hi MR.Fieldwood,

    Thank you for your reply.

    Actually, capturing packages by Wireshark has no relationship with DHCP. Please check the schedule task since you suppose something triggered it.

    We would like to suggest you start the Windows in clean boot mode due to we would also consider if any 3rd party software block it.

    https://support.microsoft.com/en-us/kb/929135

    Wish you have a nice day.

    Best Regards

    Simon


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, January 13, 2016 1:21 AM
    Moderator