An administrator has configured two VLAN interfaces: A DHCP server is connected to the VLAN10 interface. A DHCP client is connected to the VLAN5 interface. However, the DHCP client cannot get a…

Both interfaces being in different VDOMs would further isolate them and prevent DHCP communication without specific inter-VDOM links or routing.

VLAN interfaces are typically distinct Layer 2 segments identified by their VLAN ID; having the same VLAN ID would not create two distinct VLAN interfaces as described.

The role of a FortiGate interface (e.g., LAN, WAN) does not dictate its ability to function as a DHCP server or client; the issue is connectivity, not the interface's functional role.

In a FortiGate, if VLAN interfaces are configured within a virtual switch, they must belong to the same forward domain to share the same Layer 2 broadcast domain. DHCP relies on Layer 2 broadcasts, so if the client and server's VLAN interfaces are in different forward domains within a virtual switch, DHCP broadcasts cannot cross, preventing the client from receiving an IP address.