In Windows, a limited connectivity message specifically means that the host can establish a physical connection to the network but has not received a lease for an IP configuration from a DHCP server
host will be configured with an address in the automatic private IP addressing (APIPA) 169.254.x.y range
Linux host might also use APIPA, set the IP address to unknown (0.0.0.0), or just leave IP unconfigured
Steps
Establish the scope of the issue
If the issue affects multiple users, the problem is likely to be the DHCP server itself
DHCP leases take time to expire, so a problem with the DHCP server might take a few hours to manifest as different clients try to renew their leases over time
DHCP server could be offline
could have run out of available leases
forwarding between the server and clients could be improperly configured
Check the configuration of patch cords
Verify that the wall port is connected to an appropriate port on a switch via the patch panel
If the computer is not connected to an appropriate switch port,
it is unlikely to connect to the expected services, such as its default gateway, DHCP, and DNS
Check the VLAN configuration
If the switch port is not configured with the correct VLAN ID, it can have the same effect as connecting the host to the wrong switch port
Windows may also report that a network adapter has no Internet access
means that the adapter has obtained an IP configuration (or is configured statically) but cannot reach msftncsi.com to download a test file
indicates that there is an issue with either Internet access at the gateway router or name resolution
On a SOHO network, access the router management interface and verify the Internet connection via a status update page
if the link is down, contact your ISP
router may also have tools to test connectivity
Verify that it can connect to the servers configured for DNS