locked
2008 R2 DHCP server assigning addresses to Unique IDs like 3139322e3136382e33302e31323800 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a Windows 2008 R2 server running DHCP. It gives out IP addresses continuously to phantom systems with Unique IDs like 3139322e3136382e33302e31323800. It continues until it has exhausted all available IPs. I must watch it and delete these addresses as they show up. 

    They affect the available IP count, but are only listed under "Address Leases" when I reconcile.

    Thanks

    Tuesday, February 10, 2015 5:27 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    According to your description, my understanding is that the DHCP scope almost run out due to unique ID similar to 3139322e3136382e33302e31323800. And this problem occurs after  reconciling.

    The DHCP Server service stores detailed and summary IP address information in the DHCP database. When reconciling scopes, the detailed and summary entries are compared to find inconsistencies. After you select and reconcile scope inconsistencies, the DHCP Server service either restores those IP addresses to the original owner or creates a temporary reservation for those addresses. These reservations are valid for the lease time assigned to the scope. When the lease time expires, the addresses are recovered for future use.

    So, after reconciling there would be new lease appeared and may be not in use currently. You may shorten the lease duration and check to see if these lease will disappear when lease duration expired.

    Besides, have you configured the DHCP to assign IP lease to remote clients (remote access server  will obtains multi IP leases from a DHCP server at one time)?

    Best Regards,
    Eve Wang

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

    • Marked as answer by 4Fester Tuesday, February 24, 2015 10:40 PM
    Wednesday, February 11, 2015 9:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I was able to trace the problem to the Microsoft virtual wifi miniport adapter in Windows 7 laptops. Each laptop repeatedly tried to get an DHCP address. The server would think it had assigned one, but the error logs on the laptops showed as failed, will try again. They tried over and over until all available addresses were gone. I disabled the unused adapters and the problem seems to be gone. 
    • Marked as answer by 4Fester Tuesday, March 10, 2015 8:36 PM
    Tuesday, March 10, 2015 8:36 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    According to your description, my understanding is that the DHCP scope almost run out due to unique ID similar to 3139322e3136382e33302e31323800. And this problem occurs after  reconciling.

    The DHCP Server service stores detailed and summary IP address information in the DHCP database. When reconciling scopes, the detailed and summary entries are compared to find inconsistencies. After you select and reconcile scope inconsistencies, the DHCP Server service either restores those IP addresses to the original owner or creates a temporary reservation for those addresses. These reservations are valid for the lease time assigned to the scope. When the lease time expires, the addresses are recovered for future use.

    So, after reconciling there would be new lease appeared and may be not in use currently. You may shorten the lease duration and check to see if these lease will disappear when lease duration expired.

    Besides, have you configured the DHCP to assign IP lease to remote clients (remote access server  will obtains multi IP leases from a DHCP server at one time)?

    Best Regards,
    Eve Wang

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

    • Marked as answer by 4Fester Tuesday, February 24, 2015 10:40 PM
    Wednesday, February 11, 2015 9:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Eve,

    These problematic IP assignments go on with out me doing the Reconcile. If I periodically check the Statistics I see the number of available addresses dropping throughout the day. It's only after I do a Reconcile and a Refresh that the bad addresses show themselves.

    Thank you


    • Edited by 4Fester Tuesday, February 24, 2015 10:40 PM
    Thursday, February 12, 2015 8:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I was able to trace the problem to the Microsoft virtual wifi miniport adapter in Windows 7 laptops. Each laptop repeatedly tried to get an DHCP address. The server would think it had assigned one, but the error logs on the laptops showed as failed, will try again. They tried over and over until all available addresses were gone. I disabled the unused adapters and the problem seems to be gone. 
    • Marked as answer by 4Fester Tuesday, March 10, 2015 8:36 PM
    Tuesday, March 10, 2015 8:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Finally I found the solution, This problem occurs because the tap network adapter in Windows 7, 8,... . if you add deny 00 ff mac address filter, it solved. MAC address of the tap network adapter with 00 ff starts
    Tuesday, September 8, 2015 9:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had this same issue on a server 2016 dhcp server on a server 2016 host.

    Tracked it down to misbehaving iscsi on the vm host.

    Tuesday, January 9, 2018 4:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had this same issue on a server 2016 dhcp server on a server 2016 host.

    Tracked it down to misbehaving iscsi on the vm host.


    Sounds like the issue that I'm experiencing. Thanks for pointing me in that direction, but what did you do to fix the issue?
    Thursday, February 22, 2018 10:51 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    hello,

    i have the same problem on a AD 2012 R2 with the DHCP.

    Yesterday, an upgrade of my ProLiant (360G9) need to reboot the server ( VMware 6.0) , so i shut down the Fail Over Manager (FOM local) then my DHCP became full with DHCP/BOOTP type's and ID like 3139322e3136382e312e353000.

    Veeamone says:

    esx.problem.storage.iscsi.target.connect.error
    Fired by event: esx.problem.storage.iscsi.discovery.connect.error
    Event description: Échec de découverte iSCSI à 192.168.250.30 sur vmhba33.  Échec de connexion à la cible iSCSI iqn.2003-10.com.lefthandnetworks:plerin:34:vsphere sur vmhba33 @ vmk1.

    i don't know if i could fix it in that case.

    Tuesday, June 5, 2018 8:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Oddly enough, I started experiencing this when I put a ProLiant 360G9 into our environment - however, it's running hyper-v, not ESXi. Like I posted above, I thought Dougjo's post about it being iSCSI related was relevant (the Proliant with hyper-v is using iscsi storage).

    Perhaps it's specific to the 360g9 or that HP platform? I'm still experiencing this issue.

    Wednesday, July 11, 2018 3:29 PM