Website lag with 8800AXL (BT HH5 is better!)
-
- Posts: 67
- Joined: Sat Jun 02, 2012 8:21 pm
Re: Website lag with 8800AXL (BT HH5 is better!)
Sounds like you have a DNS problem, have you tried any of the public DNS servers?
-
- Posts: 6
- Joined: Wed Oct 08, 2014 7:43 pm
Re: Website lag with 8800AXL (BT HH5 is better!)
Leave off the http:// part, it's not part of the server address.
-
- Posts: 67
- Joined: Sat Jun 02, 2012 8:21 pm
Re: Website lag with 8800AXL (BT HH5 is better!)
Oops, I really should read through what I post, Well spotted.oldgrump wrote:Leave off the http:// part, it's not part of the server address.
-
- Posts: 10
- Joined: Sat May 17, 2014 5:32 pm
Re: Website lag with 8800AXL (BT HH5 is better!)
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rick>ping www.google.com -f -l 1464
Pinging www.google.com [31.55.163.152] with 1464 bytes of data:
Reply from 31.55.163.152: bytes=1464 time=29ms TTL=56
Reply from 31.55.163.152: bytes=1464 time=28ms TTL=56
Reply from 31.55.163.152: bytes=1464 time=27ms TTL=56
Reply from 31.55.163.152: bytes=1464 time=28ms TTL=56
Ping statistics for 31.55.163.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 29ms, Average = 28ms
-----------------------------------------------------------------------------------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rick>ping www.google.com -f -l 1465
Pinging www.google.com [31.55.163.250] with 1465 bytes of data:
Reply from 192.168.1.254: 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 31.55.163.250:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
2 Very different results.
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rick>ping www.google.com -f -l 1464
Pinging www.google.com [31.55.163.152] with 1464 bytes of data:
Reply from 31.55.163.152: bytes=1464 time=29ms TTL=56
Reply from 31.55.163.152: bytes=1464 time=28ms TTL=56
Reply from 31.55.163.152: bytes=1464 time=27ms TTL=56
Reply from 31.55.163.152: bytes=1464 time=28ms TTL=56
Ping statistics for 31.55.163.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 29ms, Average = 28ms
-----------------------------------------------------------------------------------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rick>ping www.google.com -f -l 1465
Pinging www.google.com [31.55.163.250] with 1465 bytes of data:
Reply from 192.168.1.254: 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 31.55.163.250:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
2 Very different results.
-
- Posts: 67
- Joined: Sat Jun 02, 2012 8:21 pm
Re: Website lag with 8800AXL (BT HH5 is better!)
Sorry, forgot about this thread.
Those results show that the MTU setting on your PC and router are set correctly. So the problem must lie elsewhere.
Have you tried temporarily disabling your antivirus and firewall software on the PC. Sometimes these can cause more grief than the nasties they are meant to protect you against.
Those results show that the MTU setting on your PC and router are set correctly. So the problem must lie elsewhere.
Have you tried temporarily disabling your antivirus and firewall software on the PC. Sometimes these can cause more grief than the nasties they are meant to protect you against.
-
- Posts: 10
- Joined: Sat May 17, 2014 5:32 pm
Re: Website lag with 8800AXL (BT HH5 is better!)
Evenings are now unusable. Opera, Chrome or IE.
Waiting forever.
Waiting forever.
-
- Posts: 10
- Joined: Sat May 17, 2014 5:32 pm
Re: Website lag with 8800AXL (BT HH5 is better!)
New firmware has sorted it (4 months after disconnecting the piece of crap).
Now perfect!
Now perfect!