Summary Downloading Google Earth requires an extra step with a server. After installation Google Earth opens several concurrent 'browser' sessions to multiple servers. If you use NTLM as an authentication method with the latest version of Google Earth, it will work fine.

However, if you are using or SSB/ISB authentication, you'll get several pop-ups asking for login information. To make Google Earth work without having to enter your username and password several times before you can use it, you need to create several Authentication Exceptions.

Get the latest science news and technology news, read tech reviews and more at ABC News.

Applies To SecureSchool, ISBossBox, LibraryDoor, Google Earth More Information An extra step is needed to download Google Earth. On the download page l Uncheck the option to install Chrome if it is there. Click the plus sign to the right 'Advanced setup' Uncheck the option 'Allow Google Earth to automatically install recommended updates'. Click 'Agree and Download' to finish downloading.

After installing Google Earth make the changes below. To create an, go to 'Website Filtering' ->'Authentication Exceptions' ->'Add A Site'.

Add entries for the following sites: • kh.google.com • keyhole.com • tools.google.com • mw1.google.com • mw2.google.com • mt0.google.com • csi.gstatic.com/csi Once you add those sites, go to 'Commit Changes' and the restart. Google Earth should now work fine.

Google Earth doesn't has means to configure a proxy server through its GUI. Def Leppard Greatest Hits Zip. So, I use an environment variable to set the proxy server. With version 6.0.3.2197 this methos worked OK, but after installing version 7.1.2.2041-r0 this no longer works. What steps will reproduce the problem? Download.deb package from Google Earth web site 2.

Install in Debian based system (tried with Debian Wheezy i386 and amd64) 3. Set environment variable http_proxy=AND HTTP_PROXY=4. Run google-earth Expected behavior (observed in version 6.0.3.2197): Connect to Google Earth servers and 'just work normally' Observed behavior: After a little time with a black screen (where I should see the Earth Globe), a notification appears statiung that 'Google Earth can't connect the login server to activate your account.

(error code c000000c)', and then another: 'Google Earth failed connect to database. The URL does not appear to be valid, or the server may be temporarily down.'

Original issue reported on code.google.com by nigles.@gmail.com on 21 Feb 2014 at 2:41. I'm starting to wonder if this is the right place for this bug report. Anyway, I'm also starting to work on ugly workarounds. I'll repeat: this is ugly, maybe it can help somebody but use at your own risk.

Now, assuming your network interface is 'eth0': 0) check that google earth is the only thing trying to reach a port 80 on a public ip: tcpdump -i eth0 -n 'tcp and not ip6 and not (src net (10 or 172.16/12 or 192.168/16) and dst net (10 or 172.16/12 or 192. Hitachi Dvd Movie Album Software. 168/16))' (it should log a ton of things, but only when google earth is running) (thanks to traffic) 1) If your proxy uses NTLM, This can create a local proxy (without authorization) that authenticates on an existing NTLM proxy. Let's stay you manage to start it on port 3128 2) (still working on it) iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 3128 This redirect all tcp traffic trying to reach a port 80 (presumably things that doesn't understand http_proxy variable) to your local port 3128, hopefully passing from ntlmaps. You'll probably need to ad a rule for port 443 too. This has a couple of issues, because it redirects ALL traffic including the one going to private ips (let's say, internal websites that normally doesn't go through proxy) (still, this is like killing a fly with an hand granade and then a cannon and then a nuke) Original comment by branco.@gmail.com on 8 Jul 2015 at 10:31.