@mfgsi, to return to your original issue - in contrary to popular belief, the DHCP server assigns the IP addresses to unique Client-ID values, not to unique source MAC addresses of the request. The Client-ID is often derived from the client's MAC address but it is not a law. So if you extend the Client-ID column of the table, you'll see that the Client-ID for each address is different (from what I can see from your screenshot, it starts with "RAS L...."; the first byte should indicate the type of the Client-ID but as it has little impact on functionality, some vendors don't care). So it seems to me that there are DHCP-clients behind the Windows server, and the Windows server acts as a DHCP relay.
The
/ip dhcp-server has a parameter called, quite counter-intuitively,
client-mac-limit. According to
the manual, this setting "
specifies whether to limit specific number of clients per single MAC address or leave unlimited (which is the default). Note that this setting should not be used in relay setups." So the name of the parameter should be something like
leases-per-mac.
Hence by setting
client-mac-limit to
1 on the DHCP server, you'll reduce the number of IP addresses leased out, but the question is what it will break at the other side of the Windows machine.