An ordinary flat home LAN normally needs one intended DHCP authority assigning its clients' network configuration. Accidentally enabling a second independent server can leave devices receiving inconsistent addresses, gateways or DNS settings.
This is a home-network operating rule, not a claim that the DHCP protocol can never involve multiple coordinated servers. Managed networks can use deliberate designs that should remain under their administrator's control.
Recognize the accidental second server
A spare router added for coverage may still run its own DHCP service. If it is connected into the LAN without a supported access-point configuration, it can answer clients unexpectedly. The result may vary depending on which response a device accepts.
Symptoms can look inconsistent: one screen works after reconnection while another has the wrong gateway, or a client changes behavior after a lease cycle. Those patterns justify checking configuration, but they do not prove a second server without evidence.
Inspect assigned configuration
On affected devices, record the local address, subnet information, default gateway and DNS settings through supported menus. Keep sensitive identifiers private. Compare them with a working device on the same intended LAN, allowing for legitimate differences such as a separate guest network.
The router's client or lease table can help identify which server owns an assignment. Do not assume two different address ranges are always wrong; a household may intentionally contain several routed networks. First establish the intended design.
Correct the role rather than guessing addresses
If a second router was intended only to provide Wi-Fi, follow its supported access-point procedure. That normally leaves the main router responsible for address assignment. Simply typing static addresses into every television can hide the symptom while leaving the underlying conflict.
Before changing roles, save the current configuration and note the management address. A mode switch can restart the device and change how its settings are reached. Make the change when an interruption is acceptable and retain a recovery route.
- Identify the intended gateway and DHCP authority.
- Compare affected and working clients on the same LAN.
- Inspect any recently added router or extender.
- Use its documented access-point or bridging configuration.
- Renew or reconnect clients and verify their new assignments.
Verify all the configuration, not just connectivity
After correction, check that clients receive the intended gateway and resolver as well as an address. Then test independent internet access and any local discovery used in the household. A successful ping to one box does not validate the complete configuration.
If you do not administer the network, report the observed assignments to the owner rather than disabling services. The useful evidence is the inconsistent configuration and when it occurs, not a speculative instruction to remove an organization's DHCP infrastructure.
Useful answers
Does DHCP only give a device an IP address?
It can also supply configuration such as gateway and DNS information. An address alone does not prove that the complete assignment is correct.
Can I fix this by giving the television a static IP?
That may conceal a symptom and can create collisions if planned badly. Correct the intended DHCP and routing roles first.