M
Martin132
I have a strange phenomenon on Server 2016. I tried this with 4 freshly installed Server 2016 computers. All the software updates were up to date (04-2018 )
As soon as I enable Microsoft ISCSI Software Initiator, the service starts and two DHCP DISCOVER broadcast messages are generated with the IP of each connected interface as source and a completely random client-mac address in the discover part of the packet.
These messages get generated at service start and roughly every 10 minutes or so. Now the problem is, due to the malformed discover request, our DHCP servers get a bit upset and exhaust the allocatable address space with nonsense reservations like these:
Client IP Address Name Lease Expiration Type Unique ID Description Network Access Protection Probation Expiration Filter Profile Policy
172.16.123.229 172.16.123.229 4/26/2018 10:14:42 AM DHCP/BOOTP 3137322e31362e3132332e32323900 Full Access N/A None
I could not reproduce this on earlier Windows Server Versions or Windows 10, so I presume it’s maybe a bug?
Or is it a feature and someone has an idea how to stop this, except firewalling port 67 on the Servers?
Continue reading...
As soon as I enable Microsoft ISCSI Software Initiator, the service starts and two DHCP DISCOVER broadcast messages are generated with the IP of each connected interface as source and a completely random client-mac address in the discover part of the packet.
These messages get generated at service start and roughly every 10 minutes or so. Now the problem is, due to the malformed discover request, our DHCP servers get a bit upset and exhaust the allocatable address space with nonsense reservations like these:
Client IP Address Name Lease Expiration Type Unique ID Description Network Access Protection Probation Expiration Filter Profile Policy
172.16.123.229 172.16.123.229 4/26/2018 10:14:42 AM DHCP/BOOTP 3137322e31362e3132332e32323900 Full Access N/A None
I could not reproduce this on earlier Windows Server Versions or Windows 10, so I presume it’s maybe a bug?
Or is it a feature and someone has an idea how to stop this, except firewalling port 67 on the Servers?
Continue reading...