Member Avatar for Google Spider

Hello all!

This is a weird problem I'm facing. I'm running Mint/XP/Ubuntu triple boot. Booted into Windows after like 2 weeks, and now I cannot access the internet from windows.:'( It Works just fine in Linux, so definitely no problem on my ISP's side. Maybe I need to reconfigure something in Windows network connections, but don't know what. (or perhaps is time to bash windows again ?:icon_frown: )


Any help will be appreciated, thanks for your time!:icon_cheesygrin:

EDIT: Oh, and definitely no viruses in there, for sure.

  • 5 Contributors
  • 6 Replies
  • 291 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by bondi007

Dani AI

Generated

Linux working while Windows cannot almost always means the ISP and the physical NIC are fine; the problem is confined to Windows (network stack, driver, DHCP/DNS, or a filtering/firewall driver). This expands on the tips from , , and and gives a compact, repeatable troubleshooting flow and what each result implies.

From an Administrator command prompt, capture basic state and run these quick tests:

ipconfig /all
ipconfig /release
ipconfig /renew
ping <gateway IP>
ping 8.8.8.8
ping google.com
nslookup google.com

Interpreting results: an address in 169.254.x.x => DHCP failure; successful ping to 8.8.8.8 but failed ping to google.com => DNS problem; failed ping to gateway => link/driver issue or NIC disabled. If DHCP fails or stacks look corrupted, reset the Windows network stack and reboot:

netsh winsock reset
netsh int ip reset

Check Device Manager (devmgmt.msc) for disabled adapters or yellow icons, then disable/enable the NIC and, if needed, uninstall and reinstall the driver from the card/vendor site. Temporarily disable or uninstall third‑party firewalls, VPN clients or security suites that install network filter drivers—these commonly block or corrupt Windows networking while leaving other OSes untouched. For PPPoE setups, verify credentials and the dialer configuration shown in Network Connections.

A single reboot restoring connectivity usually points to a transient stack/driver state. If the issue recurs, collect ipconfig /all, route print and Event Viewer entries from the failure window before making changes. Keeping NIC drivers current and knowing how to reset Winsock/TCPIP will resolve most Windows‑only connectivity failures.

Recommended Answers

All 6 Replies

Member Avatar for bondi007

Could be a driver problem? rarely happens but try re-installing the driver for you etherent or wireless depends which is your connectivity you having trouble with ;)

Member Avatar for bobbyraw

check system properties and see if the nic is disables or have a yellow ? over it. update the drive and try again

Member Avatar for hammerhead

Are you using a dhcp to assign ip's to your ethernet card? What is your isp? Also if you are using pppoe make sure that your username and password are correct :P

Member Avatar for Google Spider

Thanks for all your replies.

It started working magically when i rebooted today :D

Member Avatar for bondi007

Good to hear mate!

Bondi

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.