HELP Super Slow Internet Upload Speeds - Mainly on XP

Hi,

I have a weird issue that I hope someone can help with.

I have a Business Network connected to XLN Telecom FTTC Fibre, going through the BT Openreach Modem and a Netgear WNDR4500 Router. The Router then connects to a Netgear ProSafe Switch.
I have about 12 XP Desktops and Notebooks on my network (business so need XP really).

Recently the Microsoft Security Essentials program started crashing the PCs and hanging on the welcome screen, so I just removed it, and all was well.
A few days later ALL the XP PCs have experienced seriously slow UPLOAD Speeds when doign a Speed Test. The Fibre but it has always been slow, around 8mbps download and 2 - 4mpbs upload. On the XP machines I am getting 5mbps download but only 0.01mbps upload, with a ping of about 300ms.

Gmail and most websites work okay, but secure websites such as eBay and my website CP go really slow or time out. Some websites are also very slow, but if you us IE InPrivate or Chrome Incognito they seem to work much faster.

I thought it was the line, so changed router, factory reset modem, bypassed all the network (connecting a PC directly to the modem and router), had the ISP do line checks.
BTOpenreach have been and tested the line and equipment (they said everything seemed fine) but changed the Filter in the socket and the Modem to the latest design.

I have also tried a few virus and malware tools to make sure it is not a virus (which would be strange on ALL the PCs at the same time anyway)

2 of the guys who work for me have their own PCs (freelance) so I did the same test on theirs (Macbook Pro and Win8 PC). 6mbps download, 4.8mbps upload and 120ms ping.
The Mac seems to run fine in normal use, but the Win8 PC has a lot of issues logging into Secure Sites.

On the XP Machines, I get the same results in Chrome, IE and FireFox. On one machine with IE InPrivate it gave the same Speed Test results as the Mac / Win8 once, but now it won't replicate it.

Safe Mode speeds are exactly the same.

On my android phone, tried to log in to eBay

Connected to WiFi it took ages with some timeouts.
Connected the EE 4G it was instant.

So I did another test.

On this XP laptop I am writing on I did a speedtest using various setups

Connected to WiFi - 5.28 Download / 0.015 Upload / 273ms Ping
Connected via LAN 1 - 5.28 Download / 0.014 Upload / 232ms Ping
Connected via LAN 2 - 3.53 Download / 0.009 Upload / 503ms Ping
EE 4G WiFi Hotspot - 4.85 Download / 4.60 Upload / 459ms Ping

LAN 1 is through my Netgear Router and BT Fibre Modem.
LAN 2 is connected directly to the BT Fibre Modem with my XLN (my ISP) Router. This was using pre made RJ45 Cables.

As a further test, I found a USB WiFi Dongle so installed that on my main desktop.
Connected to LAN I get the same terrible Upload.
Connect it to the WiFi hotspot (my Android 4G Phone) and its back to normal, all websites work as they should.

Does anyone have any ideas?

Thanks

Scott

Edited by deleted (Tue 06-May-14 09:48:56)

Have you tried with just one PC connected via Ethernet and the WiFi turned off on the Netgear and without the extra switch?

I connected the XLN Router directly to the Model with LAN, missing out the rest of the network. No luck.

Should I try the same again with WiFi disabled?

Thanks

Yeap, just in case something is saturating the upload

XLN could it be an issue with their ,network like the ammount of bandwidth they are buying from BTW , ect?

Don't think so based on what has been posted

Just a thought. MTU setttings. Have you checked the settings on PCs and Router? The PCs could be fine but if the Router has been corrupted it could lead to issues.

Did some more tests for you

XP Laptop connected to XLN Technicolor Router (WiFi Disabled) then connected to Modem
12mbps Download, 0.01mbps Upload
eBay timeout

XP Laptop connected to 4G Wireless Access Point
5,42mbps Download, 2.51mbps Upload
eBay loads fine

MTU on Netgear WNDR4500 router is 1492, is that correct? As I said above, I get the same using 2 routers, and had the same issue with 2 BT Modems

XLN are supposed to be doing a 'lift and shift', but never called me back.

Thanks

1492 is correct. Can you check it on the XP machines?

In reply to a post by MHC:

Can you check it on the XP machines?

@OP: This is how: see Working out your maximum MTU for each XP PC.

I did a test using CMD, not sure if it helps

C:\Documents and Settings\>ping google.com -f -l 1400

Pinging google.com [173.194.41.130] with 1400 bytes of data:

Reply from 173.194.41.130: bytes=1400 time=29ms TTL=58
Reply from 173.194.41.130: bytes=1400 time=29ms TTL=58
Reply from 173.194.41.130: bytes=1400 time=30ms TTL=58
Reply from 173.194.41.130: bytes=1400 time=30ms TTL=58

Ping statistics for 173.194.41.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms

C:\Documents and Settings\>ping google.com -f -l 1472

Pinging google.com [173.194.41.130] with 1472 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 173.194.41.130:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\>ping google.com -f -l 1462

Pinging google.com [173.194.41.131] with 1462 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 173.194.41.131:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

There is no MTU in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip\parameters\

Thanks

C:\Documents and Settings\>ping google.com -f -l 1440

Pinging google.com [173.194.41.130] with 1440 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 173.194.41.130:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\>ping google.com -f -l 1435

Pinging google.com [173.194.41.130] with 1435 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 173.194.41.130:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\d>ping google.com -f -l 1432

Pinging google.com [173.194.41.130] with 1432 bytes of data:

Reply from 173.194.41.130: bytes=1432 time=29ms TTL=58
Reply from 173.194.41.130: bytes=1432 time=30ms TTL=58
Reply from 173.194.41.130: bytes=1432 time=30ms TTL=58
Reply from 173.194.41.130: bytes=1432 time=29ms TTL=58

Ping statistics for 173.194.41.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms

C:\Documents and Settings\RS Parkin Ltd>ping google.com -f -l 1433

Pinging google.com [173.194.41.130] with 1433 bytes of data:

Reply from 173.194.41.130: bytes=1433 time=30ms TTL=58
Reply from 173.194.41.130: bytes=1433 time=30ms TTL=58
Reply from 173.194.41.130: bytes=1433 time=30ms TTL=58
Reply from 173.194.41.130: bytes=1433 time=30ms TTL=58

Ping statistics for 173.194.41.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 30ms, Average = 30ms

C:\Documents and Settings\RS Parkin Ltd>ping google.com -f -l 1434

Pinging google.com [173.194.41.130] with 1434 bytes of data:

Reply from 173.194.41.130: bytes=1434 time=30ms TTL=58
Reply from 173.194.41.130: bytes=1434 time=29ms TTL=58
Reply from 173.194.41.130: bytes=1434 time=30ms TTL=58
Reply from 173.194.41.130: bytes=1434 time=30ms TTL=58

Ping statistics for 173.194.41.130:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms

C:\Documents and Settings\>ping google.com -f -l 1435

Pinging google.com [173.194.41.130] with 1435 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 173.194.41.130:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

So we have 1434 + 28 = 1462?

In reply to a post by XRaySpeX:

In reply to a post by MHC:

Can you check it on the XP machines?

@OP: This is how: see Working out your maximum MTU for each XP PC.

And how does that help in finding out what the MTU is actually set to?

Can you get a copy of DrTCP and run it. That will show the MTU for each interface on the PC - you can then set it to 1492 if you need to.


MTU was only a thought, I know that if I set mine to a low value the upstream speeds will drop off.

In reply to a post by ScottPk:

So we have 1434 + 28 = 1462?

Yes. the MTU setting of that PC seems to be too low at 1462.

However, I'm surprised at the 'Request timed out.' response. It should be 'Packet needs to be fragmented but DF set.'.

Can you retry with the target_name at end as specified, just in case, and use bbc.co.uk, as recommended, rather than goggle.com? I expect the trip to the States is hindering you.

You may test it manually the quick & dirty way I pointed you at or you may automate it using an application. It makes no odds; it amounts to the same thing. Whichever you are happier with.

In reply to a post by ScottPk:

There is no MTU in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip\parameters\

It'll be on some of the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip\parameters\Interfaces\xxxxxxx
or else there is something fishy going on.

Used DrTCP to change MTU from default (No Value in DrTCP) to 1492. Did a speedtest. Exactly the same, 25mbps download, 0.01mbps upload.

Then I did a Ping to bbc.co.uk

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\>ping bbc.co.uk -f -l 1464

Pinging bbc.co.uk [212.58.244.20] with 1464 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 212.58.244.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.20] with 32 bytes of data:

Reply from 212.58.244.20: bytes=32 time=19ms TTL=56
Reply from 212.58.244.20: bytes=32 time=19ms TTL=56
Reply from 212.58.244.20: bytes=32 time=18ms TTL=56
Reply from 212.58.244.20: bytes=32 time=19ms TTL=56

Ping statistics for 212.58.244.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 19ms, Average = 18ms

C:\Documents and Settings\>ping bbc.co.uk -f -l 1434

Pinging bbc.co.uk [212.58.244.20] with 1434 bytes of data:

Reply from 212.58.244.20: bytes=1434 time=22ms TTL=56
Reply from 212.58.244.20: bytes=1434 time=22ms TTL=56
Reply from 212.58.244.20: bytes=1434 time=22ms TTL=56
Reply from 212.58.244.20: bytes=1434 time=22ms TTL=56

Ping statistics for 212.58.244.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 22ms, Average = 22ms

C:\Documents and Settings\>ping bbc.co.uk -f -l 1435

Pinging bbc.co.uk [212.58.244.20] with 1435 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 212.58.244.20:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
________________________________

There are some strange things going on, but I do not know what.

My connection has dropped about 10 times this morning, with a few minutes of blackout, then it just comes back on.

Thanks for all your help so far!

Well, something's preventing it going above MTU = 1434 + 28 = 1462, but I still don't like those time-outs. I get 'Packet needs to be fragmented but DF set.' every time and I'm on XP.

What could be the cause of it?

Shall I try on my Laptop instead?

Thanks

Scott

In reply to a post by ScottPk:

What could be the cause of it?

Shall I try on my Laptop instead?

Thanks

Scott

may give more insight

http://www.elifulkerson.com/projects/mturoute.php

A recent update of MSC caused problems with windows xp systems (freezing/slow). Assume MsMpEng.exe does not appear now in services.msc
What have you replaced MSE with?

http://www.techienews.co.uk/979984/microsoft-securit...

Edited by flippery (Wed 07-May-14 22:32:39)

Does anyone have any ideas then?

XLN said this morning that BT had found a fault on the line (only took them another 2 days to come out!) and it has not fixed the issue. They have still not done the lift and shift.

I knew MSE was giving me issues! At the moment I just keep scanning with Malwarebytes and a few other scanners, but I then uninstall them, to make sure its not one of those causing these issues. Every PC I have scanned have been fine.

Thanks