last week I changed my ISP and signed into a 12 month contract which I Cab Not break with out a huge penality cost ,,,The reason for this was my previous provider I was Limited in the amount Of down load allowed =15 gig this was continually beingused up by what I was continaULLY logged into " CHERRYTAP" yeah we all say so what its is adictive hey ..well this new ISP some how connects to the net differently and Now all i see is THOSE DREADED RED X"S in place of photos .wow some are so AWESOMS LOL SO ALL friends and any one commentting to me PLEASE FOR GIVE me that i can not view now photos no coment tags nothing here just read text ,the ISPhas investigated and emailed Cherrytap with a suggestion on ways to remedy /fix the problem ,,,,I JUST have to wait to see if they will fix ,,,,,,,,,,I KNOW i am not the only aussiethat has this problem and could be many others AROUND the world that has SAME problem using CT just i happened to be determined to get something done about it and TRY and KEEP using CT as must as possible ,I WILL NOT just walk away fromCT and GIVE up using ,,,may i say that CT it proablly making bigger load on ther own servers because of the way the site in constructed ,,,,,I HOPE Baby J (Mike) soon sees the Blue shy and fixes the prob as it is a fantastic way to make Contact and Engoy time on line ...........BABY J if you red this please Fix mate
Below is the EDITED TEXT I removed the trace routes TO protect Cherry tap servers and IP addresses for PRIVACY REASONS
Baby J I am Not a dumb silly Old fart that is here to create any problems Your DITE RRRRrocks ,,,jusat maybe a change of colour scheme would be fantastic ,easy to read ,BUT YOU and YOUR Team are SENSATIONAL
Issue with some of our customers accessing images on your website - possible explanation and solution
There are a couple of things to notice :
* both of these traceroutes successfully make it to the
hop - the first at step 11,
the second at step 12.
* the successful traceroute goes only one step further to the webserver itself.
That indicates to me that there is a problem with the
"207.88.3.230.ptr.us.xo.net (207.88.3.230)" device, which is most likely
to be a router.
My guess is that a feature called Reverse Path Forwarding (RPF) has been
enabled on it. RPF requires that traffic coming into a router matches
against a router's route table entry, but won't match against a default
route entry. If the 207.88.3.230.ptr.us.xo.net router does not know
about our very large 219.90.128.0/17 address range, then the RPF check
will fail for a very large number of our customers.
If my guess is correct, the remedy to this problem is to either disable
RPF checking, or to ensure that the 207.88.3.230.ptr.us.xo.net device's
route table has all 200 000+ Internet routes.
Thanks,
Mark.
--
"I love it when a plan comes together!"
Col. John "Hannibal" Smith,
The A Team.
