Member Avatar for CrashAndBurnem

;) Ahoy!

(No I'm not a pirate)

I've been working on computers for a rather long time and personally myself nor any of my associates have come across this issue. However, on my personal computer that I recently finished building was on a seesaw back and forth between internet and no internet. As of late Ive been getting this issue more and more.

After an hour and twenty minute phone call running through tech advice from the clowns at Microsoft they left with no answer or resolution in sight. This issue that is happening currently is that Im connected through a Linksys Wireless G router and Im wired to it. Other devices such as the the computer Im typing still manages to get online along with my Xbox 360 wired as well.

Ive run all the hotfixes and still nothing.

Help?

  • 3 Contributors
  • 2 Replies
  • 111 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Member #119018

Dani AI

Generated

described a freshly built PC wired into a Linksys Wireless‑G router that intermittently loses Internet while other devices stay online. Replies from and point toward hardware and protocol-level causes; the checklist below is an evidence-first approach to narrow the fault without guessing.

During a failure collect these outputs from an elevated command prompt (capture them both when online and during the fault):

ipconfig /all
arp -a
netsh int ip show config
route print
ping <default-gateway>
ping 8.8.8.8
nslookup www.google.com
tracert 8.8.8.8
netsh winsock reset

Look for a missing or changing Default Gateway, DHCP lease abnormalities, or DNS servers that disappear. If the gateway responds but 8.8.8.8 does not, suspect DNS; if the gateway does not respond, investigate link-level issues (cable/port/NIC). arp -a can reveal duplicate IP/MAC entries. Event Viewer entries for Dhcp/Tcpip around the failure time frequently show lease or binding errors. Continuous logging such as ping -t <gateway> > C:\pinglog.txt plus periodic ipconfig /all > C:\ipcfg_before.txt will timestamp the transition and make patterns visible.

Additional isolations: check NIC power‑management and advanced driver settings (force speed/duplex if auto-negotiation looks flaky), temporarily disable third‑party firewall/AV, boot a Live Linux USB or use a USB‑Ethernet adapter to exclude Windows drivers, and review router logs/firmware for known issues. If packet-level proof is needed, capture DHCP/ARP with Wireshark during a failure to see whether renewals or ARP probes are failing. Collecting these facts will point to whether the problem is the PC (driver/stack/hardware), the local link (cable/port/duplex/duplicate IP), or router behavior.

Recommended Answers

All 2 Replies

Member Avatar for caperjack

so the new build you are connected ,wired to a wireless router ,correct .
the new build is it onboard nic or pci nic card .if onboard nic ,have you tried disabling that and using a pci nic vice versa

Member Avatar for Member #119018

Try disabling IPv6. That has worked in a few cases I've seen.

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.