3/31/2014

Chromecast and Netflix Outside the US

So you already have a provider that enables you to view Netflix from outside the US, but your Chromecast refuses to play movies from Netflix?

The reason for this is that the Chromecast uses fixed DNS servers (8.8.8.8 and 8.8.4.4).

You could use iptables on your router to redirect these addresses to your preferred DNS server. BUt ypur router may not support iptables.

Here's a solution without iptables: most routers will support setting up static routes, so all it takes is to add routes for the above addresses that refer to a non-existent address in you LAN. When the Chromecast detects that its known DNS servers are unreachable, it falls back to what you have configured in your router.

I tested this approach with my FritzBox, and it works like a charm.

P.S.: Could be that this loophole will be close soon; Google were pretty quick to fix the root exploit that served similar purposes.

3/12/2014

Chechens, Ingush and Dagestani Also Ready to Vote on Their Nationality

Grozny, Magas, Makhachkala - Could the vote of the Crimean population about their nationality be the next export/import hit? Separatists from the Russian republics of Chechnya, Ingushetia and Dagestan described the planned referendum as the "best idea that Putin ever had." Now the residents of the North Caucasus provinces want to vote on their nationality on 16 March, at the same time as the Crimea. The Russian population of the three republics is between 0.8 and 3.6 percent.

The original article is much longer, and in German, it can be found here.

And just in case it was not obvious: this is satire.
 

SharePoint: "Attempted to use an object that has ceased to exist"

I got this error after migrating sites from SharePoint MOSS 2007 to SharePoint 2013.

Problem
The scenario: a document library that uses a lookup to another list and allows multiple values to be selected

The effect: when you have the lookup column as part of your view of the document library, you get the  error message: "Attempted to use an object that has ceased to exist". When you remove the column from the view, it works just fine.

With new sites in SharePoint 2013, the above does not happen, the issue is related to migrated sites only!

Solution
While I have not been able to identify the root cause, I have found the following workaround:
change all columns of type "People" in the document library from "Name (with presence)" to "Name" only.

I have no clue why this makes a difference, but it does!

Kudos
And here is where I got this hint from - thank you so much!
The post also mentions that "Microsoft is now evaluating if they will create a hotfix for this." dating from November 2013.

Non-Kudos (or whatever the opposite of kudos may be)
So far, there is not hotfix and SP1 did not fix it :-(


adaxas Web Directory