The problem with this is i'm sure it could be one of millions of things but i hope someone else has thought of something i havent.

Problem: I was using the internet then all of a sudden it cut off, and gave me the "limited to no connectivity". This is on my desktop computer which is hard wired to a hub then to the modem. I have tried:

-enable/disable, iprelease/renew, rollback driver, install new driver, tried different "fix" patches from microsoft(what they say if i have this prob), I even went as far as reformatting the computer and putting win xp back on. but nothing changes. tomorrow i'll head out and buy a new eithernet card to try that

thats really all i can think of now because it doesn't have anything to do with the connection. i'll take the cable from my computer with"limited to no conn." and plug it straight into my laptop and internet works just fine on the laptop.

any ideas? thanks

Dani AI

Generated

A quick synthesis of the thread: reports the desktop shows "limited or no connectivity" while the same cable works on a laptop, and a replacement Ethernet card did not change the result. Replies from and covered the obvious network- and cable-level checks. With those already done, the next troubleshooting should separate Windows from hardware and surface low-level link/DHCP behavior or hidden filter drivers.

A decisive, low-effort isolation is to boot a Linux live image (USB/CD) and test the link and DHCP there — it proves whether the NIC/hardware path is healthy outside of Windows. Also observe the NIC link/activity LEDs and try a different physical port or a USB-to-Ethernet adapter; LED states often reveal negotiation/collision faults that software cannot. A Windows-only test is to boot Safe Mode with Networking to disable third-party filters and virtual adapters.

Useful Windows and Linux checks (look for DHCP server, default gateway, APIPA 169.254.x.x, and ability to ping external IPs):

# Linux (live image)
ip addr show
sudo dhclient eth0
ping -c 3 8.8.8.8
# Windows (admin CMD)
ipconfig /all
ping 127.0.0.1
netsh winsock reset
netsh int ip reset C:\resetlog.txt

If the live Linux session gets an IP and the desktop can ping outside, the cause is Windows-level (winsock/NDIS filter, virtual adapters, or service bindings). If Linux also fails, suspect motherboard/slot, switch/hub port, or modem/router DHCP binding. Additional checks: examine Event Viewer for DHCP/TCPIP errors, disable any virtual VPN or bridge adapters, try a different PCI slot or a USB NIC, and test the desktop on a different network (or via phone tethering) to rule out local DHCP/MAC-binding issues.

Recommended Answers

All 3 Replies

New Card gives me the same problem.....????

your ISP maybe might be down?
Bad cable? - buy a new one and see
Are your IP settings correct (dhcp/fixed ip)

first off: Switch hub for switch.

Try connecting your computer directly to the modem. Does this work? If so, you know it's not your computer.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.