Re: Plusnet Slow web browsing MTU change!

ahhhh. ok. took a look again at my settings and looked at an article in
computershopper mag. It states to ping -f -l packketsize Gateway of
ISP.

So I put my router back to automatic which now reports that auto is set
to 1492. I then did a ping -f -l 1372 195.166.128.53 and got the DF
message back.

I had to drop away down to 1372 before I did not get a DF message.

ping -f -l 1373 195.166.128.53

Pinging 195.166.128.53 with 1373 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 195.166.128.53:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping -f -l 1372 195.166.128.53

Pinging 195.166.128.53 with 1372 bytes of data:

Reply from 195.166.128.53: bytes=1372 time=94ms TTL=123
Reply from 195.166.128.53: bytes=1372 time=95ms TTL=123
Reply from 195.166.128.53: bytes=1372 time=95ms TTL=123
Reply from 195.166.128.53: bytes=1372 time=95ms TTL=123

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


As you can see below, my router is going the whole way up to 1472
before it sends the DF message.
ping -f -l 1473 192.168.1.1

Pinging 192.168.1.1 with 1473 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 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping -f -l 1472 192.168.1.1

Pinging 192.168.1.1 with 1472 bytes of data:

Reply from 192.168.1.1: bytes=1472 time=14ms TTL=255
Reply from 192.168.1.1: bytes=1472 time=14ms TTL=255
Reply from 192.168.1.1: bytes=1472 time=3ms TTL=255
Reply from 192.168.1.1: bytes=1472 time=14ms TTL=255

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

What I don't know though is my PC, router, Exchange, ISP is at fault.

Can someone shed some light on this please.

.

Relevant Pages

  • Re: XP Home Networking Help
    ... Ping statistics for 192.168.0.4: ... "IBM-09E436C483A ping 192.168.0.4" ... Pinging 192.168.0.4 with 32 bytes of data: ... "IBM-09E436C483A ping Compaqqqqq" ...
    (microsoft.public.windowsxp.network_web)
  • Re: Wireless problem
    ... Ethernet adapter Local Area Connection: ... Ping to DNS: ... Pinging 66.94.9.120 with 32 bytes of data: ... Ping statistics for 66.94.9.120: ...
    (microsoft.public.windowsxp.network_web)
  • Re: Destination Host Unreachable
    ... Ping statistics for 143.166.11.10: ... Persistent Routes: ... Pinging 143.166.170.10 with 32 bytes of data: ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: IE Routing Problem
    ... Set the client box MTU to 1492 and the firewall's MTU to 1492. ... Here's what I get when I run the ping you describe: ... Packet needs to be fragmented but DF set. ... >> routers generally provide for an MTU setting? ...
    (microsoft.public.win2000.dns)
  • Re: IE Routing Problem
    ... Set the client box MTU to 1492 and the firewall's MTU to 1492. ... Here's what I get when I run the ping you describe: ... Packet needs to be fragmented but DF set. ... >> routers generally provide for an MTU setting? ...
    (microsoft.public.win2000.networking)