<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>VPN on Holyarmy.org</title>
		<link>https://holyarmy.org/tags/vpn/</link>
		<description>Recent content in VPN on Holyarmy.org</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Mon, 15 Jun 2009 23:13:25 +0000</lastBuildDate>
		
			<atom:link href="https://holyarmy.org/tags/vpn/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>VPN on Ubuntu Linux with Juniper Network Connect</title>
				<link>https://holyarmy.org/2009/06/vpn-on-ubuntu-linux-with-juniper-network-connect/</link>
				<pubDate>Mon, 15 Jun 2009 23:13:25 +0000</pubDate>
				<guid>https://holyarmy.org/2009/06/vpn-on-ubuntu-linux-with-juniper-network-connect/</guid>
				<description>&lt;p&gt;There’s one standard document on HOWTO get Network Connect working on Ubuntu Linux. It’s mad scientist’s doc: &lt;a href=&#34;http://mad-scientist.us/juniper.html&#34;&gt;http://mad-scientist.us/juniper.html&lt;/a&gt; . However, there are a few things not covered. I’ll assume that you’ve followed mad scientist’s excellent guide before going any further.&lt;/p&gt;&#xA;&lt;h3 id=&#34;issue-1-64-bit-ubuntu&#34;&gt;Issue #1: 64-bit Ubuntu&lt;/h3&gt;&#xA;&lt;p&gt;By default, when you install java on your 64-bit system, you get a 64-bit java. No surprise there, right? Well, Juniper’s tools don’t play nice with 64-bit java. If you attempt to start the &lt;strong&gt;junipernc&lt;/strong&gt; script you’ll promptly see the “VPN has failed!” error message.&lt;figure id=&#34;attachment_400&#34; style=&#34;width: 204px&#34; class=&#34;wp-caption alignnone&#34;&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Fight Back! (When VPN Clients Mis-Behave)</title>
				<link>https://holyarmy.org/2008/07/fight-back-when-vpn-clients-mis-behave/</link>
				<pubDate>Wed, 23 Jul 2008 18:20:19 +0000</pubDate>
				<guid>https://holyarmy.org/2008/07/fight-back-when-vpn-clients-mis-behave/</guid>
				<description>&lt;p&gt;I have to use VPNs at work. Specifically, to access my production webservers (etc), I have to use a Cisco VPN client. Sadly, the VPN concentrator overrides my choice of allowing local LAN access. So, when I am on the VPN, I have my DNS options changed so I can’t use any local servers. This is a serious, serious pain. So painful in fact, that many times instead of fight with it, I simply would run a Windows session in VMware (on my Mac) and connect the VPN there. This has drawbacks too, but it’s better than not having local network access.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Beating the Cisco VPN Client Error 51 On Leopard</title>
				<link>https://holyarmy.org/2008/07/beating-the-cisco-vpn-client-error-51-on-leopard/</link>
				<pubDate>Tue, 22 Jul 2008 16:10:01 +0000</pubDate>
				<guid>https://holyarmy.org/2008/07/beating-the-cisco-vpn-client-error-51-on-leopard/</guid>
				<description>&lt;p&gt;I had this error popup today on my Mac OS X Lepopard 10.5.4 machine.&lt;/p&gt;&#xA;&lt;img class=&#34;alignnone size-medium wp-image-309&#34; title=&#34;vpnerr51&#34; src=&#34;https://holyarmy.org/files/2008/07/vpnerr51.png&#34; alt=&#34;Cisco VPN Client Error 51&#34; /&gt;&#xA;&lt;p&gt;This is not cool as, well, I NEED MY VPN TO WORK!&lt;/p&gt;&#xA;&lt;p&gt;Thankfully google came to my rescue. The solution is to execute the following in Terminal:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;sudo /System/Library/StartupItems/CiscoVPN/CiscoVPN restart&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Thanks for the answer, &lt;a href=&#34;http://virtuallyshocking.com/2008/06/26/cisco-vpn-client-error-51-after-leopard-1053-upgrade/&#34;&gt;VirtuallyShocking.com&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Network Directory Services</title>
				<link>https://holyarmy.org/2007/10/network-directory-services/</link>
				<pubDate>Sat, 06 Oct 2007 21:00:41 +0000</pubDate>
				<guid>https://holyarmy.org/2007/10/network-directory-services/</guid>
				<description>&lt;p&gt;Network directory services are core to Internet functionality. The &lt;a href=&#34;http://en.wikipedia.org/wiki/Domain_Name_System&#34;&gt;Domain Name System (DNS)&lt;/a&gt; provides a global (and/or local) directory of hosts and services. &lt;a href=&#34;http://en.wikipedia.org/wiki/LDAP&#34;&gt;Lightweight Directory Access Protocol (LDAP)&lt;/a&gt; servers can provide some of the same information as DNS (or be used to back DNS), but are more frequently used to create network user databases, store user group information, providing centralized account information and password storage.&lt;/p&gt;&#xA;&lt;p&gt;I recently completed an upgrade of these two core services on a network I manage. We had been running outdated (but functional) &lt;a href=&#34;http://en.wikipedia.org/wiki/BIND&#34;&gt;BIND&lt;/a&gt; v8 and &lt;a href=&#34;http://en.wikipedia.org/wiki/Openldap&#34;&gt;OpenLDAP&lt;/a&gt; v2.0 instances for of DNS and LDAP servers. Also, throw a Windows Server 2003 into the mix, which, as an &lt;a href=&#34;http://en.wikipedia.org/wiki/Active_directory&#34;&gt;Active Directory&lt;/a&gt; domain controller has to run its own DNS and LDAP (AD is tweaked LDAP) servers.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
