<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Terminal Server without VPN for remote access</title>
	<atom:link href="http://www.1stbyte.com/2005/03/20/terminal-server-without-vpn-for-remote-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.1stbyte.com/2005/03/20/terminal-server-without-vpn-for-remote-access/</link>
	<description>Company site for Greg Fischer { GregTheGeek }</description>
	<lastBuildDate>Tue, 09 Mar 2010 05:12:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Greg</title>
		<link>http://www.1stbyte.com/2005/03/20/terminal-server-without-vpn-for-remote-access/comment-page-1/#comment-541</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Wed, 03 Mar 2010 16:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.1stbyte.com/2005/03/20/terminal-server-without-vpn-for-remote-access/#comment-541</guid>
		<description>Using a VPN would require you to essentially &quot;Dial-up&quot; a connection to your remote network. For example, you might be at home, and your work network has software on their end allowing you to connect to them.  Using that established connection, you basically become a remote node on their network. (that&#039;s one of the main reasons I don&#039;t like VPN&#039;s.)  

Using a remote access solution is different, although technically they are still creating some sort of a tunnel for you to securely connect. The difference is, you are not connected as a remote computer on the work network, you are only making a very specific secure connection to a specific port and specific computer. Not the same as a VPN tunnel, where you basically open up all ports and re-route your communications to the work net.  What I prefer is a program like GoToMyPC, or my favorite, LogMeIn.com.  They act as a third party to &quot;broker&quot; a connection from your home system to the work system. They do this in an outbound-connection only scenario.  What I mean by that is, you don&#039;t open ports up on a firewall and re-route traffic to certain internal systems. (another security hole, possibly)  In the LogMeIn setup, it makes an outbound connection without any inward firewall rules.  You connect at home to LogMeIN, they know where the work computers is, and they create the connections between the two for you.  IMHO, more secure that way.

Does that help?  I am not familiar with proxynetworks, but it looks like some similar connection methods as GoToMyPC or LogMeIn.

I might add too, that even though you would still create an inward connection with a firewall rule, I would still greatly prefer an SSH tunnel to another internal system.  Like creating your SSH connection with a port forward to RDP on your work desktop. (I wrote a program to do that actually!)  But since I&#039;ve discovered LogMeIn, I prefer that the most, it&#039;s just way to easy, no servers and firewalls to manage at the work end.  But no matter what, unless there is an actual practical requirement for using a VPN (and I can&#039;t think of one that SSH can&#039;t handle, in regards to remote access), I stay far away from VPN&#039;s.  That is, unless you desire to connect to remote networks, then sure, VPN sounds great.</description>
		<content:encoded><![CDATA[<p>Using a VPN would require you to essentially &#8220;Dial-up&#8221; a connection to your remote network. For example, you might be at home, and your work network has software on their end allowing you to connect to them.  Using that established connection, you basically become a remote node on their network. (that&#8217;s one of the main reasons I don&#8217;t like VPN&#8217;s.)  </p>
<p>Using a remote access solution is different, although technically they are still creating some sort of a tunnel for you to securely connect. The difference is, you are not connected as a remote computer on the work network, you are only making a very specific secure connection to a specific port and specific computer. Not the same as a VPN tunnel, where you basically open up all ports and re-route your communications to the work net.  What I prefer is a program like GoToMyPC, or my favorite, LogMeIn.com.  They act as a third party to &#8220;broker&#8221; a connection from your home system to the work system. They do this in an outbound-connection only scenario.  What I mean by that is, you don&#8217;t open ports up on a firewall and re-route traffic to certain internal systems. (another security hole, possibly)  In the LogMeIn setup, it makes an outbound connection without any inward firewall rules.  You connect at home to LogMeIN, they know where the work computers is, and they create the connections between the two for you.  IMHO, more secure that way.</p>
<p>Does that help?  I am not familiar with proxynetworks, but it looks like some similar connection methods as GoToMyPC or LogMeIn.</p>
<p>I might add too, that even though you would still create an inward connection with a firewall rule, I would still greatly prefer an SSH tunnel to another internal system.  Like creating your SSH connection with a port forward to RDP on your work desktop. (I wrote a program to do that actually!)  But since I&#8217;ve discovered LogMeIn, I prefer that the most, it&#8217;s just way to easy, no servers and firewalls to manage at the work end.  But no matter what, unless there is an actual practical requirement for using a VPN (and I can&#8217;t think of one that SSH can&#8217;t handle, in regards to remote access), I stay far away from VPN&#8217;s.  That is, unless you desire to connect to remote networks, then sure, VPN sounds great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.1stbyte.com/2005/03/20/terminal-server-without-vpn-for-remote-access/comment-page-1/#comment-540</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Wed, 03 Mar 2010 16:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.1stbyte.com/2005/03/20/terminal-server-without-vpn-for-remote-access/#comment-540</guid>
		<description>Can you elaborate on what the differences are between using a VPN and &lt;a href=&quot;http://www.proxynetworks.com&quot; rel=&quot;nofollow&quot;&gt;remote access&lt;/a&gt; software? What are the advantages/disadvantages of both...or is one just a more dressed up version of the other?</description>
		<content:encoded><![CDATA[<p>Can you elaborate on what the differences are between using a VPN and <a href="http://www.proxynetworks.com" rel="nofollow">remote access</a> software? What are the advantages/disadvantages of both&#8230;or is one just a more dressed up version of the other?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
