Kudos to the various sites that provided some guidance on getting the Cisco IPSec VPN client going again on Windows 10. I finally was able to get it going for me. I’m running Windows 10 64bit and connecting to Cisco IPSec/UDP.
1. Run Winfix.exe before you do anything else. This will nuke all the bad stuff you probably did to try and get it operational. Do this first before you start piling on installs again. Trust me. Believe me. Reboot.
2. Install the Dell Sonic VPN client. Reboot.
3. Install your Cisco VPN client. Reboot
4. Try the VPN connection. It should work.
I know there are various other sequences out there, but this one is the only one that worked for me.
Here are some of the other sites I tried prior to going down this route. Any sequence that included the DNE update from Citrix didn’t work for me.
If you ever find an abandoned Linux server running WordPress on your network that was left for dead but still running somehow, here are some tips on what to do. I just went through this and was amazed when I discovered the WordPress install wasn’t compromised.
1. Get root. Kind of goes without saying. Get console and if you don’t have the root password to the box, you’re not going anywhere.
2. Get mysql root. WordPress is probably running mysql as a the backend db. If you don’t have that, reset it.
3. Get into mysql at the command-line and find the wordpress db to get to the wp-users table.
4. Your db is probably titled “wordpress” but it could be a variant of that.
5. Select the wp-users table in your WordPress db and reset the password for the ID =1 user.
mysql> select ID, user_login, user_pass from wp_users;
6. Reset that password in the table for the ID 1 entry
mysql> update wp_users SET user_pass = MD5('newpass') WHERE ID=1 LIMIT 1;
7. That should give you login to the old WordPress site (http://www.site.com/wp-admin/) via the browser.
After you are able to login, I wish you the best. Unpatched WordPress sites are a constant target for bots in need of sites to host malware, so you are very lucky if you find the site has not been compromised. When I logged-in, I found a WordPress 3.2 site which puts it at about 4 years old against the release history.
I’ve read The Atlantic off and on for many years in print and online. The sure is a regular stop for me on daily news and I’ve appreciated many of their articles over the years. I’ve tweeted and linked to their content dozens if not hundreds of times over the years.
When I hit their site tonight, they seem to be taking a new approach to visitors. They started dishing the ad-blocker shame banner.
I understand the concept. They want to shame me into some conversion. But here is the thing, I took a few seconds to try and close the image to get to content but I just gave up and left. Isn’t that what most will end up doing?
I understand the predicament they must be in, but I struggle to see how executing a barrier like this would generate a reader to become a paying customer.
Shame and barriers can’t be the right approach can it?
After attending a game where the Giants got hammered by Atlanta wearing their #FadeToBlack alternative black uniforms, I wondered what their record was in games with different uniforms. I was surprised this little tidbit of information wasn’t tracked along side other crazy data that baseball nuts tend to fixate on. I kept looking and found that someone did! Sportslogos.net tracks this. Pretty neat for all us data folks to get another aspect into the mix.
They track on logos, unis, and other visual aspects of the game. It’s a great resource and worth bookmarking.