Member Avatar for hussulinux

I am using XP SP2,

My internet from LAN via a router stops after 30 mins.
All downloads, pings etc stop.
Only option is to restart...

output of netstat -an is below


Active Connections

Proto Local Address Foreign Address State
TCP LISTENING
TCP LISTENING
TCP LISTENING
TCP 127.0.0.1:1051 LISTENING
TCP 127.0.0.1:1117 127.0.0.1:1118 ESTABLISHED
TCP 127.0.0.1:1118 127.0.0.1:1117 ESTABLISHED
TCP 127.0.0.1:1119 127.0.0.1:1120 ESTABLISHED
TCP 127.0.0.1:1120 127.0.0.1:1119 ESTABLISHED
TCP LISTENING
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP FIN_WAIT_1
TCP FIN_WAIT_1
TCP LAST_ACK
TCP ESTABLISHED
TCP TIME_WAIT
TCP TIME_WAIT
TCP LAST_ACK
TCP TIME_WAIT
TCP TIME_WAIT
TCP TIME_WAIT
TCP LAST_ACK
TCP TIME_WAIT
TCP TIME_WAIT
TCP TIME_WAIT
TCP TIME_WAIT
TCP TIME_WAIT
TCP ESTABLISHED
TCP TIME_WAIT
TCP LAST_ACK
TCP TIME_WAIT
TCP ESTABLISHED
TCP LAST_ACK
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP LAST_ACK
TCP LAST_ACK
TCP TIME_WAIT
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP LAST_ACK
TCP ESTABLISHED
TCP ESTABLISHED
TCP ESTABLISHED
TCP SYN_SENT
TCP ESTABLISHED
TCP SYN_SENT
UDP *:*
UDP *:*
UDP *:*
UDP *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1025 *:*
UDP *:*
UDP *:*
UDP *:*


Any ideas

  • 2 Contributors
  • 3 Replies
  • 232 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by DaveB

Dani AI

Generated

Brief follow‑up and practical checks (adds to ’s suggestions and to what reported)

The netstat dump in the original post shows many peer‑to‑peer style connections (several ports around 6881 and lots of ESTABLISHED / TIME_WAIT / LAST_ACK entries). That pattern often causes consumer routers to run out of connection‑tracking entries or overload their CPU — the router then stops forwarding new traffic even though the PC’s stack still looks active. Reinstalling Windows removes any OS‑side corruption, but the underlying failure mode can be either an overloaded router or a local network stack problem.

Quick, ordered checks to reproduce and diagnose the fault

  • Confirm whether the LAN stays up when the Internet “drops” by continuously pinging the gateway:

    ping -t 192.168.1.1

    If the gateway replies but external pings fail, the router/WAN is the likely culprit. If the gateway itself stops replying, check the NIC and switch.

  • When the problem appears, try to reach the router admin page. If you can, inspect the router’s active connection/session count or logs for errors or a crash.

  • Temporarily stop any P2P/bit‑torrent clients or reduce their simultaneous‑connection settings (many clients allow limiting peers/connections). If stopping them prevents the drop, the router is being overloaded.

  • Repair the Windows TCP stack if you suspect OS corruption (requires reboot after):

    netsh winsock reset
netsh int ip reset

  • Update the NIC driver and disable any NIC power‑saving option in Device Manager. As noted, firmware updates for the router are a sensible long‑term step (follow the vendor’s instructions).

Longer‑term fixes: limit P2P concurrency, use a router with larger NAT/connection capacity, or move heavy P2P traffic behind a router that supports many simultaneous sessions.

Recommended Answers

All 3 Replies

Member Avatar for DaveB

Could be a short lease on the DHCP, (give your PC an IP address).

To check this, when you loose your connection try this procedure.

Start > Run >

cmd

.

In the command box, type the following

ipconfig /all

to check the LAN connection status, then

ipconfig /release

followed by

ipconfig /renew

to renew your IP Lease.

If that works then post back here for a permanent fix, or configure a manual IP address if you know how.

You could try updating the Routers Firmware, the software and procedure will be available from the manufacturers website, but not the easiest thing to do.

Regards, Dave

Member Avatar for hussulinux

I had another PC with fresh windows and it worked there. So I reinstalled Windows and it works fine.


Could be a short lease on the DHCP, (give your PC an IP address).

To check this, when you loose your connection try this procedure.

Start > Run >

cmd

.

In the command box, type the following

ipconfig /all

to check the LAN connection status, then

ipconfig /release

followed by

ipconfig /renew

to renew your IP Lease.

If that works then post back here for a permanent fix, or configure a manual IP address if you know how.

You could try updating the Routers Firmware, the software and procedure will be available from the manufacturers website, but not the easiest thing to do.

Regards, Dave

Member Avatar for DaveB

Sry I couldn't be of help, but glad you sorted it.

Regards, Dave

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.