<?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: Getting Serious About VNC</title>
	<atom:link href="http://variableghz.com/2008/09/getting-serious-about-vnc/feed/" rel="self" type="application/rss+xml" />
	<link>http://variableghz.com/2008/09/getting-serious-about-vnc/</link>
	<description>For the technically inclined.</description>
	<lastBuildDate>Mon, 23 Jan 2012 11:51:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: How-To: Make Use of UltraVNC SC (Single-Click) &#124; VariableGHz</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-6966</link>
		<dc:creator>How-To: Make Use of UltraVNC SC (Single-Click) &#124; VariableGHz</dc:creator>
		<pubDate>Mon, 20 Jun 2011 04:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-6966</guid>
		<description>[...] IP, or you can lock it down using something like DynDNS, similar to the way you normally do with UltraVNC. I strongly recommend you lock it down using DynDNS, and the DynDNS Updater on your system. So, [...]</description>
		<content:encoded><![CDATA[<p>[...] IP, or you can lock it down using something like DynDNS, similar to the way you normally do with UltraVNC. I strongly recommend you lock it down using DynDNS, and the DynDNS Updater on your system. So, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Windows Home Server is Incredibly Awkward &#124; VariableGHz</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-3507</link>
		<dc:creator>Windows Home Server is Incredibly Awkward &#124; VariableGHz</dc:creator>
		<pubDate>Wed, 29 Sep 2010 23:56:54 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-3507</guid>
		<description>[...] So, to begin, I click Windows Home Server Console and a wizard takes you through the steps of setting up the Console. It was simpler than I expected, considering the awkward and unfriendly UI experience it started with. Once it got to the remote access and Internet accessibility of the Console, however, things came to a halt. Cleverly, WHS tries to enable UPnP (Universal Plug and Play) in your router to make things easy. However, just like with ActiveX, UPnP was/is the cause of many security exploits and malware so by default, many routers have UPnP disabled &#8212; including the one I am using. So, I enabled UPnP on this Netgear router and then the wizard was able to proceed, however, it still briefly flashed  that orange exclamation mark icon before stating that everything was A-OK and later on down the line it would tell me periodically that remote access functionality wasn&#8217;t working. To fix it, I would click repair and it would show me a spinny wheel for a while, then, somehow, it would be fine&#8230; for a while. Fortunately, I don&#8217;t rely on gimmicky &#8220;remote access&#8221; hubs/add-ins, I use the real deal: UltraVNC. [...]</description>
		<content:encoded><![CDATA[<p>[...] So, to begin, I click Windows Home Server Console and a wizard takes you through the steps of setting up the Console. It was simpler than I expected, considering the awkward and unfriendly UI experience it started with. Once it got to the remote access and Internet accessibility of the Console, however, things came to a halt. Cleverly, WHS tries to enable UPnP (Universal Plug and Play) in your router to make things easy. However, just like with ActiveX, UPnP was/is the cause of many security exploits and malware so by default, many routers have UPnP disabled &#8212; including the one I am using. So, I enabled UPnP on this Netgear router and then the wizard was able to proceed, however, it still briefly flashed  that orange exclamation mark icon before stating that everything was A-OK and later on down the line it would tell me periodically that remote access functionality wasn&#8217;t working. To fix it, I would click repair and it would show me a spinny wheel for a while, then, somehow, it would be fine&#8230; for a while. Fortunately, I don&#8217;t rely on gimmicky &#8220;remote access&#8221; hubs/add-ins, I use the real deal: UltraVNC. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thijs</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-82</link>
		<dc:creator>thijs</dc:creator>
		<pubDate>Sun, 07 Dec 2008 12:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-82</guid>
		<description>Nice! 
So, the first time the IP-adress of the server will change, I will notice if I configured it all the right way. That will be the first time I will be happy with a change of IP-adress!

Thanks!!</description>
		<content:encoded><![CDATA[<p>Nice!<br />
So, the first time the IP-adress of the server will change, I will notice if I configured it all the right way. That will be the first time I will be happy with a change of IP-adress!</p>
<p>Thanks!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-79</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 07 Dec 2008 03:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-79</guid>
		<description>Hey there,

That&#039;s precisely the reason for DynDNS and UltraVNC! By default, DynDNS will check for a change in your IP every 5 minutes, if there is a change, it will make an update to the hostname. By default, it will &quot;force&quot; an update within 25 days. You shouldn&#039;t have to manually deal with your IP ever again.

I am glad you&#039;re able to use DynDNS and VNC together in this way. It&#039;s a near-perfect solution.

-Admin</description>
		<content:encoded><![CDATA[<p>Hey there,</p>
<p>That&#8217;s precisely the reason for DynDNS and UltraVNC! By default, DynDNS will check for a change in your IP every 5 minutes, if there is a change, it will make an update to the hostname. By default, it will &#8220;force&#8221; an update within 25 days. You shouldn&#8217;t have to manually deal with your IP ever again.</p>
<p>I am glad you&#8217;re able to use DynDNS and VNC together in this way. It&#8217;s a near-perfect solution.</p>
<p>-Admin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thijs</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-72</link>
		<dc:creator>thijs</dc:creator>
		<pubDate>Sat, 06 Dec 2008 08:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-72</guid>
		<description>Hello,

Thank you for your information.
I still have a question. But I will explain my &quot;server situation&quot; first.

I have a server at a location which I normally never visit. I use VNC Viewer to acces this server using the IP adress. The IP adress is dynamic. When it has changed, I have to travel to my server connect a monitor, look at the new IP adres and go home again. 

I&#039;ve now made a dyndns account and installed the dyndns client on my server. I&#039;ve also linked the service to the dyndns account, and I can connect to my server by entering the hostname.

But:
When the IP-adress of the server will change again, will these Dyndns tools update my IP-adress automatically. So that I can still connect to my server using the hostname?

And if not, how can I make it possible that I don&#039;t have to travel to my server every time the IP-adress has changed?

Thank you!</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Thank you for your information.<br />
I still have a question. But I will explain my &#8220;server situation&#8221; first.</p>
<p>I have a server at a location which I normally never visit. I use VNC Viewer to acces this server using the IP adress. The IP adress is dynamic. When it has changed, I have to travel to my server connect a monitor, look at the new IP adres and go home again. </p>
<p>I&#8217;ve now made a dyndns account and installed the dyndns client on my server. I&#8217;ve also linked the service to the dyndns account, and I can connect to my server by entering the hostname.</p>
<p>But:<br />
When the IP-adress of the server will change again, will these Dyndns tools update my IP-adress automatically. So that I can still connect to my server using the hostname?</p>
<p>And if not, how can I make it possible that I don&#8217;t have to travel to my server every time the IP-adress has changed?</p>
<p>Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ernesto Wilkinson</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-10</link>
		<dc:creator>Ernesto Wilkinson</dc:creator>
		<pubDate>Thu, 13 Nov 2008 00:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-10</guid>
		<description>x7ftsqff3391zypc</description>
		<content:encoded><![CDATA[<p>x7ftsqff3391zypc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wafer</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-7</link>
		<dc:creator>Wafer</dc:creator>
		<pubDate>Thu, 09 Oct 2008 22:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-7</guid>
		<description>I tried all day long to get this working.
I use a brand new Router Netgear DGNB2100 with insuccess.
I tried to open and forward all port.
I opened also all VNC ports using UPnP port mapping software and... nothing again.
When I connect with the client to server it fail.

I&#039;m getting crazy I&#039;m start thinking probably is the brand new router that may have some firmware problems.

:(</description>
		<content:encoded><![CDATA[<p>I tried all day long to get this working.<br />
I use a brand new Router Netgear DGNB2100 with insuccess.<br />
I tried to open and forward all port.<br />
I opened also all VNC ports using UPnP port mapping software and&#8230; nothing again.<br />
When I connect with the client to server it fail.</p>
<p>I&#8217;m getting crazy I&#8217;m start thinking probably is the brand new router that may have some firmware problems.</p>
<p>:(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-6</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 06 Oct 2008 20:56:55 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-6</guid>
		<description>Mr. Garoo,

Thanks for your comment. I didn&#039;t say that TightVNC does not have those features, but rather UltraVNC has the least disadvantages and in my opinion is the most stable of the VNC flavors. Moreover, the last time I tested TightVNC, which admittedly was a long time ago, it lacked numerous features such as the chat, file-transfer, ability to send custom-keys, etc. I apologize if this information seems incorrect, but note that I did not state that TightVNC lacks these features but only that UltraVNC does in fact have them and they work well.</description>
		<content:encoded><![CDATA[<p>Mr. Garoo,</p>
<p>Thanks for your comment. I didn&#8217;t say that TightVNC does not have those features, but rather UltraVNC has the least disadvantages and in my opinion is the most stable of the VNC flavors. Moreover, the last time I tested TightVNC, which admittedly was a long time ago, it lacked numerous features such as the chat, file-transfer, ability to send custom-keys, etc. I apologize if this information seems incorrect, but note that I did not state that TightVNC lacks these features but only that UltraVNC does in fact have them and they work well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angel</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-5</link>
		<dc:creator>Angel</dc:creator>
		<pubDate>Sun, 05 Oct 2008 17:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-5</guid>
		<description>pues la neta gracias he esto me ayudo demsiado ojala explicaran todo asi</description>
		<content:encoded><![CDATA[<p>pues la neta gracias he esto me ayudo demsiado ojala explicaran todo asi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ran Garoo</title>
		<link>http://variableghz.com/2008/09/getting-serious-about-vnc/comment-page-1/#comment-4</link>
		<dc:creator>Ran Garoo</dc:creator>
		<pubDate>Fri, 03 Oct 2008 21:18:15 +0000</pubDate>
		<guid isPermaLink="false">http://variableghz.com/?p=5#comment-4</guid>
		<description>Your information in re tightVNC is incorrect.

Always had native ctr-alt-del, file transfer and much more.

Extremely easy to set up and works like a charm in secure connections whether
ssh, ssl,stunnel, putty: what have you.</description>
		<content:encoded><![CDATA[<p>Your information in re tightVNC is incorrect.</p>
<p>Always had native ctr-alt-del, file transfer and much more.</p>
<p>Extremely easy to set up and works like a charm in secure connections whether<br />
ssh, ssl,stunnel, putty: what have you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

