Only my computer can't get internet other devices are normal.
I have a very weird issue, every device in my house can connect to the internet, except my computer. If I check the network status on Windows 11 I get "DHCP server isn't responding" error, which is weird because my brother's computer has no issue at all.
For topology we have:
ISP Modem > AX 73 using Dynamic IP (double NAT setup but using different IP ranges) > TP-Link Switch > Mine and my brother's computers.
We also have some satellite devices using Easymesh but they are not being used by my computer.
My brother's computer works flawlessly and the Wireless internet also works perfectly.
For testing sake I connect an Intelbras Twibi on the switch (Brazilian mesh device) and then connected my computer on it, I instantly got internet even if this is a triple NAT setup. I'm out of ideas, I'm about just setting a fixed IP to my PC to see if it fixes the issue.
EDIT: Tried to set a fixed IP to my PC and still can't use the internet. I'm using NextDNS by the way, but I don't think this is DNS related, when I connect my PC on the Twibi device using the very same DNS settings I have no issues.
EDIT2: Tried to directly connect my computer on the Switch (the desktop IP is fixed on the TP-Link but internally on the PC I'm using DHCP).
@Joseph-TP Hello, thanks for the tips.
My conputer is using the automatic IP assigment and a manual DNS because I use the NextDNS service.
I decided to fix the IP of my computer in the AX73 settings while keeping the dynamic IP on my computer and I didn't have the issues again. I'm not sure if this was the solution or something else fixed the underlying cause, but it seems that I have no issues again.
@Joseph-TP Hello, thanks for the tips.
My conputer is using the automatic IP assigment and a manual DNS because I use the NextDNS service.
I decided to fix the IP of my computer in the AX73 settings while keeping the dynamic IP on my computer and I didn't have the issues again. I'm not sure if this was the solution or something else fixed the underlying cause, but it seems that I have no issues again.