[Snap] Trouble accessing CDN Content on new connection

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] Trouble accessing CDN Content on new connection

Draizuh

4 posts

Wannabe Geek

#104950 23-Jun-2012 12:32

So ive had NDSL setup twice in the past month, once with slingshot (ugh) and now with snap. Trouble is ive had the same issue on both ISPs (and a friend in town had it on telecom)

My connection through to snap is fine, and i can access most websites however, any website that uses a CDN (ie facebook,tumblr,speedtest.net) do not load. the title appears in the browser however it just hangs on a CDN address (ie. c.speedtest.net), this is however on my Windows XP SP3 Netbook, Tumblr and facebook will load on my macbook however certain elements wont.

My MTU is set to 1492 (as high as it allows) and i have tried MSS clamping as described here to no aval. anyone got any insights? Its either a problem at a cabinet or my router (which is a D-link DSL-2730B T1). I spoke to the chorus installer and he said he switched ports when he did the install for snap..

Im at a bit of a loss so any ideas would be ace!

McGee

200 posts

Master Geek

#645091 23-Jun-2012 13:10

The first thing I would recommend to check would be your DNS servers.

I'm sure you already have but just putting it out there, If they're not Snap's DNS servers then they won't know how to reach local CDN content.

Second of all try dropping your MTU to 1400 and see what happens, Most of us run 1492 I think but I noticed mine's a bit more responsive on 1400 for whatever reason.

Good luck!

Draizuh

4 posts

Wannabe Geek

#645112 23-Jun-2012 14:20

Yep, already checked them! it was the same issue on slingshot too, and i tried ihug DNS as well which were open (according to a thread on this forum) and no change, ditto with googles DNS.

My MTU was at 1400 But i could try it again and see if i can get a better response.

[Edit: No different on a MTU of 1400]

Kraven

729 posts

Ultimate Geek

#645123 23-Jun-2012 14:47

Just a thought... there was an issue with the DSL-2730B working correctly in NZ when it was launched here. I'm not sure if the issue ever was resolved as we simply gave up completely on DLink DSL products after the hassles with this particular model.

Anyway, try disabling ADSL2 support by following these instructions:

http://files.dlink.com.au/products/DSL-2730B/REV_A/SetupGuides/DSL-2730B_How_to_connect_via_ADSL1.pdf

If that solves the issue and you want ADSL2+ speeds I would recommend getting a different router. TPLink's are good.

Draizuh

4 posts

Wannabe Geek

#645130 23-Jun-2012 14:56

Nope same issue persists. :(

McGee

200 posts

Master Geek

#645913 25-Jun-2012 14:58

Id say it would have to be an issue inside your network either being PC or Modem.

Wouldn't make any sense having that issue over that many ISPs.
It's extremely unlikely to be an issue with the port on the exchange / cab as all that traffic is being passed straight back / tunnled to the ISP.

If you can swap the modem out that's what I would say to try first.

Let us know how you get on.

Draizuh

4 posts

Wannabe Geek

#645930 25-Jun-2012 15:47

Yes thats what ive now narrowed it down to, seems odd that similar things were happening at another location with a different modem though
anyone know what dicksmith are like dealing with refunds on a faulty router??

McGee

200 posts

Master Geek

#645942 25-Jun-2012 15:58

Normally pretty good if you've got proof of purchase etc