0

Discussion topic: Failed remote network problem

Reply
Reply
This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

Thanks. A conspiracy theorist would say, hang on...after weeks, we have a solution...

And every time it's posted it GETS DELETED?

 

I'm not a conspiracy theorist, but, really.....?

 

If anyone wants the solution they can message me.

 

I won't be advertising, campaigning, maligning, swearing, identifying...just posting THE SOLUTION...

This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

 

      *********VICTORY***********?!

 

Perhaps some help for those in my position...

 

Pointing my Sky box to my router's IP address... gives a 50% download failure rate

 

However, if I point it to my mini PC...On there, I have Simple DNS Pro installed...which has a free trial.

 

(Other DNS forwarders are available. I mention this one purely to show people the exact settings I used to solve this problem)

 

Via 'tools', 'options', 'forwarding'...

I have put in domain name: a2047.sky

and forwarded to DNS server 1.1.1.1

 

I have put in domain name:
a.2047.sky.akami.net

and forwarded to DNS server 1.1.1.1

 

No idea why that works. But it does!

 

I can see the program's activity log is very, well, active, so it is in play, doing something..22 out of 22, Season 1 Young Sheldons...no errors...22 out of 22 Series 2, Young Sheldons...no errors. 22 Season 1 Seal Team, no errors

 

If I point my Sky box DNS back to my router, everything falls apart

 

I've previosuly pointed the Sky box DNS to 1.1.1.1 and it hasn't worked, so I don't know why asking a Mini PC to do so would be different?

 

I'm hoping these settings might help with setting up my cheap router!

 

Can any network bods make any sense of this accidental victory?

 

It's certainly nothing Sky or Kloud9 has done because it falls over when pointed to my router...

Was this a fluke? No...if I put 1.1.1.1 in to the Sky box, it all falls apart again?!?!

This message was authored by Chodley This message was authored by: Chodley

Re: Failed remote network problem

Posted by a Superuser, not a Sky employee. Find out more

Yeah I totally don't understand why that works. Maybe Mark does?

This message was authored by Anonymous This message was authored by: Anonymous

Re: Failed remote network problem

Do you still have an entry in MARAS for the name "ondemand.cdnselector.skycdp.com" pointing to the 87. IP address?

This message was authored by Anonymous This message was authored by: Anonymous

Re: Failed remote network problem

and if you reply no to the question below, then sorry, i dont think you have fixed this at all, and I will explain after you reply/answer

This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

I

t wasn't actually Maras...it was the program I'm now using...and no, we deleted it on the basis that it was the one that worked.

 

I put the other two in because they didn't. It was only that you or Chodley or both mentioned 1.1.1.1 that I slapped it in

 

I remain no expert, but a PC saying go to 1.1.1.1 shouldn't be any different from a Sky box saying the same?!?

 

They're on the same network, so Sky still know it's Kloud9 calling!

 

Interestingly, I've just lost the internet briefly...'download failed' popped up...and all the Sky menus lamented the lack of internet...it resolved within seconds and the download self corrected and carried on...previously a download was the end of the road for the episode concerned...

 

All quite interesting!

This message was authored by Anonymous This message was authored by: Anonymous

Re: Failed remote network problem

Ok, as I've beensaying, you need your DNS server to Send ALL DNS quries to 1.1.1.1 not just the couple you chose.

Then you need a static Host entry for the download site.

 

The fault we all seem to have is that sometimes we get a good ip and sometimes bad. - this equates to a few mins of working and then a few of not etc.

 

With your current solution, you are still relying on 1.1.1.1 for DNS BUT you are DNS caching. This means your server will store a DNS lookup for a period of time (depending on the TTL value)

 

So you've gone from a set up that failed for a few mins, to work for a few mins, and now have a set up that in theory will work for say a day, and then break for a day. randomly. When your cached entry expires, and the DNS server goes back out to resolve, it could get a working or non working IP and it would then cache that.

 

not a permanent fix.

Until you force your SKY box to avoid Akamai, you havent resolved this.

This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

 

Damn!

 

This program isn't the long term solution. You're right...leaving a PC on 24/7 isn't great

 

I'm sure it might not be relevant, but the software does have a 'cache data received in responses from others DNS servers'...I've set that to 10 years in case it's relevant!

 

This is quite the journey...

 

This is the bit that confuses and confounds...

 

'You need your DNS server to Send ALL DNS quries to 1.1.1.1 not just the couple you chose.

Then you need a static Host entry for the download site'

 

I'm hoping Cisco router will let me do that!

 

That's for your continued insight...I won't ring Sky and Kloud9 to get them to stand down...if they ever stood up...

 

 

 

 

 

This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

Ok...I've directed that program to send ALL to 1.1.1.1

 

Additionally, I've found the windows host file and added both domain names and the IP address we want them sent to (87.248.204.0)

 

Now, how do I tell if my accidental fix is in play, or this fix fix is in play ?!?

This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

Wellz that fell apart quickly.

 

Kudos to Mark for predicting the inevitable failed remote network failure...

 

Gonna reverse to waiting for the postman to bring my router...

 

I can see now why 8888, 8844 and 1111 worked for some...for a short time. I was on a role there for a morning!

 

 

This message was authored by Anonymous This message was authored by: Anonymous

Re: Failed remote network problem

I gave instructions the other day to run on another pc to show exactly what this DNS server is doing and what the responses are. I'd suggest doing that and posting actual responses, rather than just downloading stuff.

This message was authored by Anonymous This message was authored by: Anonymous

Re: Failed remote network problem

With any product, or a router you need the same thing

 

One forwarder for all unresolved queries, this should go to 1.1.1.1

 

Then you need a Host Entry or A record.

 

With that software you would likely need a zone for the FQDN and an A record, in the zone, with the IP address.

 

By the way, where is that router coming from China by boat???

This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

Hi,

 

It's coming via eBay...Sadly, it's so cheap they didn't want to spend more by sending it quickly.

 

Theres a group of people here with clearly technical knowledge who presume I have it. I don't

 

It's gonna need...'use this program...go to this setting...type this'...type of instructions to get me over this line...

This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

The lead has just arrived, so we're getting there!

 

The Sky update is they remain committed to resolving this (Hey, a network pun!)

This message was authored by Craigv9 This message was authored by: Craigv9

Re: Failed remote network problem

When I use Simple DNS Plus to lookup

 

ondemand.cdnselector.skycdp.com

 

I get 87.248.205.0

 

Slightly different from what I was expecting...

 

87.248.204.0

 

And when I use Simple DNS Plus to look up


a2047.sky.akamai.net

I get:

95.101.64.115
95.101.54.99
95.101.64.121
95.101.54.123
95.101.54.122
95.101.54.114
95.101.54.113
95.101.54.112
95.101.54.120

 

Which is all Swiss Cheese to me!

 

 

Reply

Was this discussion not helpful?

No problem. Browse or search to find help, or start a new discussion on Community.

Start a new discussion

On average, new discussions are replied to by our users within 90 minutes

New Discussion