- Check if the Network Interface Card (NIC) is disabled.
If it is, enable it. - Verify the IP address status.
If the NIC is enabled, check whether it says “Media Disconnected”, or the device has a valid IP address or an APIPA address (169.254.x.x). - If it says Media disconnected, it may indicate a Layer 1 issue (physical connectivity).
Check the Ethernet cable, switch port, or Wi-Fi SSID connection status to ensure the device is properly connected. - If there is a physical connection problem (Layer 1), fix it first. Then check again if the device obtains an IP address.
- If the device has an APIPA address, investigate the DHCP server—either on the router or another DHCP server in the network.
- Troubleshoot the DHCP service.
Make sure it is enabled and functioning correctly and not exhausted. Restart the service if necessary. - Once the device obtains a valid IP address (NOT APIPA), test internet connectivity.
If it still doesn’t work, check whether the device can communicate with the default gateway (router or firewall). - Verify gateway communication.
Try to ping the gateway. If NOT successful, check your router or firewall, make sure they are functioning, do a restart if needed,
- Once you get successful ping response from the gateway proceed to test communication with a public IP (e.g., 8.8.8.8).
- If the device cannot reach a public IP, check the WAN (internet) connection.
Ensure the WAN port is active, plugged in, and has a valid public IP address from the ISP. Liaise with ISP. - If the WAN connection is confirmed to be working by ISP, try pinging a public IP address like 8.8.8.8 or 1.1.1.1.
If this works, it means routing to the internet is functional. - However, if internet access is still not working, it might be a DNS issue.
Most users access websites using domain names (e.g., google.com), not IP addresses. - To confirm a DNS issue, try pinging or browsing to a website (e.g., google.com, youtube.com, sularyslab.com).
If it fails, check the DNS server settings on the device. Ensure the DNS server is reachable and functional.
A quick fix is to set the DNS to Google’s public DNS (8.8.8.8).
If using a private DNS, verify that the DNS service is up and running.