Wow. Thanks so much for your thoughtful assessment; your observation was spot on. I thought there was some larger problem, but the cause was a problem on 2nd dhcp server, as you suggsted. The "compare" gave me the clue:
admin@router# compare
[edit service dhcp-server shared-network-name LAN1]>authoritative enable
[edit service dhcp-server] <<
+shared-network-name LAN2_IoT { << SOMETHING'S NOT RIGHT HERE!
+ authoritative enable <<
+}
[edit service dhcp-server shared-network-name VLAN.1003]>authoritative enable
[edit]
It all worked perfectly, with the right network name: LAN2-IoT vs LAN2_IoT.
admin@router# set service dhcp-server shared-network-name LAN1 authoritative enable [edit] admin@router# set service dhcp-server shared-network-name LAN2-IoT authoritative enable [edit] admin@router# set service dhcp-server shared-network-name VLAN.1003 authoritative enable [edit] admin@router# compare [edit service dhcp-server shared-network-name LAN1]>authoritative enable [edit service dhcp-server shared-network-name LAN2-IoT]>authoritative enable [edit service dhcp-server shared-network-name VLAN.1003]>authoritative enable [edit] admin@router# commit [ service dhcp-server ] Stopping DHCP server daemon... Starting DHCP server daemon... [edit] admin@router#
