Windows client is getting wrong IP

Please follow the below template, it will help us to help you!

Expected Behaviour:

My lan is on the 192.168.0.xxx subnet. Pihole (192.168.0.6) is the dhcp server and can issue IPs in the range 192.168.0.100 - 192.168.0.200
All clients connecting to the LAN (via WiFi or Ethernet) should get a valid IP in the above mentioned range

Actual Behaviour:

My Windows 11 laptop and a Windows 10 PC are both getting an IP in the range 192.168.100.xxx subnet.

Debug Token:

https://tricorder.pi-hole.net/UgbHOkKY/

Some more information:
The router is connected to a Switch. The Switch is connected to an AP via Ethernet. My Macbook Pro and the Windows laptop are both connected to the AP. The Macbook pro is able to access the network and the Internet.
The Windows Laptop is unable to connect.

On checking the DHCP logs, I see the following:

Feb 8 21:40:02 dnsmasq-dhcp[6161]: DHCPNAK(eth0) 192.168.100.106 90:81:58:82:41:a2 wrong network
Feb 8 22:07:54 dnsmasq-dhcp[6161]: DHCPNAK(eth0) 192.168.100.123 e4:0d:36:70:c5:0b wrong network
Feb 8 22:11:04 dnsmasq-dhcp[6161]: DHCPNAK(eth0) 192.168.100.123 80:c5:f2:93:b7:7d wrong network
Feb 8 22:11:23 dnsmasq-dhcp[6161]: DHCPNAK(eth0) 192.168.100.123 80:c5:f2:93:b7:7d wrong network
Feb 8 22:13:28 dnsmasq-dhcp[8229]: DHCPNAK(eth0) 192.168.100.123 80:c5:f2:93:b7:7d wrong network

The bold line is the Windows laptop.
I've also set a static IP in the 192.168.0.xxx range on the laptop and it then is able to connect to the network and the Internet.

Some more information:

pi@raspberrypi:~ $ sudo pihole-FTL dhcp-discover
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds

  • Received 548 bytes from eth0:192.168.100.1
    Offered IP address: 192.168.100.126
    Server IP address: N/A
    Relay-agent IP address: N/A
    BOOTP server: (empty)
    BOOTP file: (empty)
    DHCP options:
    Message type: DHCPOFFER (2)
    server-identifier: 192.168.100.1
    lease-time: 86400 ( 1d )
    netmask: 255.255.255.0
    router: 192.168.100.1
    dns-server: 192.168.100.1
    domain-name: "pihole"
    --- end of options ---

  • Received 304 bytes from eth0:192.168.0.6
    Offered IP address: 192.168.0.164
    Server IP address: 192.168.0.6
    Relay-agent IP address: N/A
    BOOTP server: (empty)
    BOOTP file: (empty)
    DHCP options:
    Message type: DHCPOFFER (2)
    server-identifier: 192.168.0.6
    lease-time: 86400 ( 1d )
    renewal-time: 43200 ( 12h )
    rebinding-time: 75600 ( 21h )
    netmask: 255.255.255.0
    broadcast: 192.168.0.255
    domain-name: "pihole"
    dns-server: 192.168.0.6
    dns-server: 192.168.0.6
    router: 192.168.0.1
    --- end of options ---

DHCP packets received on interface eth0: 2

I'm not really sure what the first block of information means.
I also don't recognize the offered IP address of 192.168.0.164. There is no client with that IP (as far as I can see in the Pi hole DHCP page's " Currently active DHCP leases" section

You have another router (192.168.100.1) in your network acting as DHCP server:

* Received 548 bytes from eth0:192.168.100.1
    (...)
    router: 192.168.100.1
    dns-server: 192.168.100.1

192.168.0.164 was offered to your Pi-hole, but Pi-hole is already using another IP (192.168.0.6), so this address wasn't accepted and no devices are currently using it.
This is normal.

Thank you. I isolated each AP on the network and reset and reconfigured them. That fixed the issue.

I'm not sure on what changed on the AP as it was working fine until few days ago and I'd not made any changes to its settings