Embedded jpg links do not load

[ljz1]

I am slowing ripping all my hair out on this one. We have a tylink ONS 150 csu connected to Cisco 2501 (all ACL removed). Links to jpg do not load, even if you do a 'show picture'. For example

http://www.downstreammedia.net/TheRangeLife/PhotoHoldem/Round3/HobieJudge.jpg

on site

http://www.therangelife.blogspot.com.

If copy/paste url into browser it loads!
It is not PC/browser specific because you can take the PC off the network and the page loads fine. All PC behind the router are effected. Has anyone seen anything like this before? No one can figure it out!

Laurie

 

[Fatty99]

ljz1,

This is probably a problem with MTU size. This could be client-side, server side or on 1 of the routers on the path.
U could try a couple of things.
1. lower mtu size on client side
2. enable path mtu discovery on client
3. increase mtu size on your router.

If the problem is caused on path it will be more difficult to figure this out.

U could check the MTU on every router of the whole path.
Traceroute the path.
Check the MTU to every hop on the path

MTU can be found by using icmp echos (ping) with DF bit set to 1.
MTU size example belowe for last hop (destination)= 1464 + 28 = 1492
Do this for every hop. This way you can figure


ping

http://www.downstreammedia.net

-f -l xxxx
Increase xxxx till packets are fragmented

C:\WINDOWS>ping

http://www.downstreammedia.net

-f -l 1464

Pinging downstreammedia.net [64.202.163.179] with 1464 bytes of data:

Reply from 64.202.163.179: bytes=1464 time=236ms TTL=46

Ping statistics for 64.202.163.179:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 236ms, Maximum = 236ms, Average = 236ms
Control-C
^C
C:\WINDOWS>ping

http://www.downstreammedia.net

-f -l 1465

Pinging downstreammedia.net [64.202.163.179] with 1465 bytes of data:

Packet needs to be fragmented but DF set.

Ping statistics for 64.202.163.179:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
^C


If this does not locates the problem. The problem probably will be caused on the route back (server ---> client). Then the above actions need to be done from server to client/IP. Only possible if u have control of server or server admin wants to help you out.


Fatty