Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


casewindow

310 posts

Ultimate Geek
+1 received by user: 4


#208405 10-Feb-2017 11:13
Send private message

When I run a speedtest on my Windows 10 PC, it affects my ADSL2 router WAN performance. The other non-Win10 machines on the network show slow Speedtests until the Win10 machine is rebooted.

 

I have the following config

 

  • Router: TP-Link TL-8960n (ADSL2) - Also tried on a TP-Link 8840 (ADSL2)
  • TP-Link Gigabit switches and Belkin 10/1000 switches
  • Static IP: DHCP disabled except for a very small range with MAC addresses assigned to that range.
  • Wireless access points: a range of TP-Link 802.11n wireless access points
  • Mixture of Windows 10, Vista, FreeBSD, Raspbian, iOS on the network

Up until recently this was all working fine, then I rebooted my Raspberry Pi (which has always had difficulty connecting via wifi, but did have an uptime of 74 days). Since then the network has been unstable with ADSL connectivity dropping. However, even with the Raspberry Pi off I can re-create an issue where running a speedtest from the windows 10 machine somehow seems to "contaminate" the ADSL performance until that win10 machine is rebooted.

 


Weird.





Q6600 @ 3.2Ghz (400x8) | GA-X38-DQ6 | 4Gb Corsair Dominator@800Mhz 4-4-4-12 | HIS HD5870 | Creative X-fi Fatality Pro | 2xWD SATAII Caviar Black 640Gb / 1xSeagate SATAII 7200.12 1000Gb | 2xASUS IDE DVDRW | Silverstone OP1000 PSU | Silverstone TJ09 Case

Create new topic
jamesrt
1663 posts

Uber Geek
+1 received by user: 941

ID Verified
Trusted
Lifetime subscriber

  #1718293 10-Feb-2017 13:17
Send private message

Possible you have a duplicate IP address - especially if you're not using DHCP.

 

Basically, that'll cause packets to go to the "wrong" device, and if the clashing machine is also using the LAN address of the ADSL router, then that definitely won't be good...

 

First step would be to check all the static configurations to ensure they are using unique address space.

 

As a second step, you may want to consider powering ALL end-user devices off (or at least unplugging cables, and disconnecting WiFi) and then reconnect / turn on one-at-a-time until you hit the issue again.  Possible faulty hardware could be doing strange things with respect to "layer 2" (i.e. physical) access to the network - broadcasts / noise / generally taking up the bandwidth leaving little for "real" work.  Doing this should help isolate or eliminate that as being a factor.


Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.