<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: Linksys SSL VPN and places that block ActiveX in Virtual Private Networking</title>
<link>http://www.dslreports.com/forum/r20272142</link>
<description></description>
<language>en</language>
<pubDate>Sat, 30 Aug 2008 04:44:21 EDT</pubDate>
<lastBuildDate>Sat, 30 Aug 2008 04:44:21 EDT</lastBuildDate>

<item>
<title>Re: Linksys SSL VPN and places that block ActiveX</title>
<link>http://www.dslreports.com/forum/remark,20272142</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Could you explain how Active X modules are blocked by a "place"?  Was the IP address of the server providing the Active X module blocked?  Was a port being blocked?  Specifying what was being blocked will allow people to suggest workarounds.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20272142</guid>
<pubDate>Wed, 02 Apr 2008 18:59:38 EDT</pubDate>
</item>

<item>
<title>Linksys SSL VPN and places that block ActiveX</title>
<link>http://www.dslreports.com/forum/remark,20256237</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I had been riding high, thinking my SSL VPN to my house was all that and a bag of chips....  Then, I think what went wrong, is that I was a guest at a place that doesn't let ActiveX modules be downloaded.  (I had trouble running it via Firefox too, which doesn't use ActiveX, of course).<br><br>It's either the place blocking, or my biggest mistake, my "Windows ME 2007" (Vista) deciding to add extra blockage because it was a public network, but I'm pretty sure it was the place, not the machine.)  <br><br>Any workarounds to that?  I was so excited to not run into problems with places that blocked IPSEC VPN Ports, I didn't think about places blocking Active X.<br><br>Thanks!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20256237</guid>
<pubDate>Mon, 31 Mar 2008 07:06:38 EDT</pubDate>
</item>

</channel>
</rss>
