ClearOS 7.5 is working as a gateway in my home network. Suddenly, the only Windows client in the network has stoped accessing the network!
It's a Windows 10 running on a laptop. The WiFi connects to the network, but gets wrong IP, gateway and DNS addresses. I flushed the Windows caches and restarted the DHCP client, but still the machine cannot get addresses from the clearOS DHCP server. It connects though if I disabled DHCP auto mode and manually enter the addresses.
I tried to connect the laptop to another network and it worked flawlessly there! Only with clearOS it fails to automatically get the addresses from the DHCP server.
I checked the server and found no traces of the laptop in the DHCP leases table nor in the Intrusion Prevention System.
The Windows machine is manually connecting to the network now, but I really want to make it connects automatically. I'd appreciate any help in this regard.
Thank you.
It's a Windows 10 running on a laptop. The WiFi connects to the network, but gets wrong IP, gateway and DNS addresses. I flushed the Windows caches and restarted the DHCP client, but still the machine cannot get addresses from the clearOS DHCP server. It connects though if I disabled DHCP auto mode and manually enter the addresses.
I tried to connect the laptop to another network and it worked flawlessly there! Only with clearOS it fails to automatically get the addresses from the DHCP server.
I checked the server and found no traces of the laptop in the DHCP leases table nor in the Intrusion Prevention System.
The Windows machine is manually connecting to the network now, but I really want to make it connects automatically. I'd appreciate any help in this regard.
Thank you.
In DHCP Server
Share this post:
Responses (2)
-
Accepted Answer
Thank you Nick. Yes, the issue was caused by one AP in the network. It suddenly decided to work as a DHCP server by its own!
By the way, if anyone uses Linksys AP and encounters such an issue, then this page can be of help. It's a known "feature" (bug) in their APs! -
Accepted Answer
Thank you Nick. Yes, the issue was caused by one AP in the network. It suddenly decided to work as a DHCP server by its own!
By the way, if anyone uses Linksys AP and encounters such an issue, then this page can be of help. It's a known "feature" (bug) in their APs!
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »