General discussion

  • Creator
    Topic
  • #2073802

    BAD_ADDRESS listing under Active Leases

    Locked

    by featsfanbob ·

    We recently installed DHCP on our NT 4.0 network and is running successfully. When I pull up active leases under the DHCP manager, however, I see a number of addresses which are listed as BAD_ADDRESS. These are not addresses we excluded from the scope and they are not reserved or broadcast addresses. What does this entry mean?

All Comments

  • Author
    Replies
    • #3894380

      BAD_ADDRESS listing under Active Leases

      by Anonymous ·

      In reply to BAD_ADDRESS listing under Active Leases

      Either someone is using static addresses that are duplicates to the one listed as BAD_ADDRESS’s or turn off DHCP logging, since there is a bug.

    • #3894364

      BAD_ADDRESS listing under Active Leases

      by calves ·

      In reply to BAD_ADDRESS listing under Active Leases

      I noticed those address while back, but after chasing the the IP and owner, I found to be the other servers, using those IP for various connections into the server where the DHCP resides. So, a left it alone.
      I hope that points you in the right direction.

      Good Luck!

    • #3894329

      BAD_ADDRESS listing under Active Leases

      by wirejockey ·

      In reply to BAD_ADDRESS listing under Active Leases

      Run “WINIPCFG” (on Win9x PC’s, IPConfig on NT) and click on “Release All” then click on “Renew All”. You may find that some PCs may not release the address, in my experience, waiting until the lease expired cleared the problem. You may not want to wait that long. Warning: do not delete your current scope and create a new one UNLESS you first release all IP addresses on your network. Good Luck!

    • #3894317

      BAD_ADDRESS listing under Active Leases

      by jun1cez1 ·

      In reply to BAD_ADDRESS listing under Active Leases

      To featsfanbob,

      I may have to refresh you in TCP/IP addressing then. In tcp/ip, if the last octet of the node address falls into all zero’s and all one’s, its a bad address. I mean, let say,

      network.network.network.00000000 or
      network.network.network.11111111

      are consider bad address and not being recognized at all. So, I suggest that you revisit your addressing scheme.

      Good luck.

      Jun

Viewing 3 reply threads