<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: Cannot connect to VPN and do not know why</title>
	<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why/</link>
	<description>Comments on Ask MetaFilter post Cannot connect to VPN and do not know why</description>
	<pubDate>Fri, 15 Sep 2006 06:37:25 -0800</pubDate>
	<lastBuildDate>Fri, 15 Sep 2006 06:37:25 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>Question: Cannot connect to VPN and do not know why</title>
		<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why</link>	
		<description>Why can I not VPN in consistently to work? &lt;br /&gt;&lt;br /&gt; It DOES work on WinXP Pro w/ Windows Firewall on:&lt;br&gt;
-directly plugged into Comcast Cable modem&lt;br&gt;
-unsecured WiFi connection downtown&lt;br&gt;
-using Verizon Wireless phone as modem for DUN&lt;br&gt;
&lt;br&gt;
It DOES NOT work on WinXP Pro w/ or w/o Windows Firewall on:&lt;br&gt;
-behind Linksys WRT54G wireless router, either plugged into it or using wireless connection, even when all VPN, IPSEC options are set to enable pass through and the firewall on the device is disabled&lt;br&gt;
-plugged into a port on my alma mater&apos;s network&lt;br&gt;
&lt;br&gt;
When it does not work, it just says connecting to (IP ADDRESS)... and eventually times out after several minutes.&lt;br&gt;
&lt;br&gt;
I have looked all over the internet and not found a solution that makes sense since this happens on networks without the Linksys device.  No other user has this issue, other than my boss (also new to company) and he has tried the same attempt methods, other than the college&apos;s connection.&lt;br&gt;
&lt;br&gt;
Please help!  Much appreciated!</description>
		<guid isPermaLink="false">post:ask.metafilter.com,2006:site.46552</guid>
		<pubDate>Fri, 15 Sep 2006 06:13:00 -0800</pubDate>
		<dc:creator>criticman</dc:creator>
		
			<category>wireless</category>
		
			<category>vpn</category>
		
			<category>network</category>
		
			<category>wired</category>
		
			<category>linksys</category>
		
			<category>router</category>
		
			<category>firewall</category>
		
			<category>ipsec</category>
		
	</item> <item>
		<title>By: sohcahtoa</title>
		<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why#709750</link>	
		<description>What kind of VPN? I&apos;ve got more experience with Checkpoint, older versions of that can be a real beast. Normally make sure you&apos;re using the newest version of the VPN client, unless your IT group says to use an older version for compatiblity (Hello, Checkpoint pre-NG!).&lt;br&gt;
&lt;br&gt;
Make sure the linksys is at the most recent firmware. Try to dial down the MTU on the system (I&apos;ve had problems where an ISP was silently dropping large ipsec packets) - but don&apos;t leave that setting if it doesn&apos;t help. Try to change the private IP range of your linksys to something unusual (99% will be set up for 192.168.1.0/24, change yours to 192.168.187.0/24 or 10.4.5.0/24 for example - older Checkpoint VPNs that don&apos;t use Office Mode get confused by multiple connections from the same NAT space, or if your private network is the same range as the corprate network).&lt;br&gt;
&lt;br&gt;
When testing with the linksys, concentrate on when you&apos;re plugged in so as to not muddy the waters. I wouldn&apos;t concentrate on the connection from the university since that might be prohibited by policy.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.46552-709750</guid>
		<pubDate>Fri, 15 Sep 2006 06:37:25 -0800</pubDate>
		<dc:creator>sohcahtoa</dc:creator>
	</item><item>
		<title>By: chuma</title>
		<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why#709770</link>	
		<description>Is UPnP port forwarding enabled on your WRT54G?  Windows XP will try to open the appropriate VPN port(s) on your router using UPnP (assuming you are using the standard Windows VPN connection type, also known as PPTP).&lt;br&gt;
&lt;br&gt;
Ditto what sohcahtoa said about the university connection: they probably have stuff locked down enough that it won&apos;t work from there no matter what you do.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.46552-709770</guid>
		<pubDate>Fri, 15 Sep 2006 06:57:25 -0800</pubDate>
		<dc:creator>chuma</dc:creator>
	</item><item>
		<title>By: paulsc</title>
		<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why#709855</link>	
		<description>VPN clients and servers are not all interchangeable. Speculating on possible causes without knowing what VPN client you are using, and with what VPN server you are trying to connect isn&apos;t likely to be helpful. So:&lt;br&gt;
&lt;br&gt;
1) What VPN client are you using?&lt;br&gt;
2) What VPN server is your company using?&lt;br&gt;
3) What corporate firewall are you going through?&lt;br&gt;
4) What revision of your WRT54G firmware are you running?&lt;br&gt;
&lt;br&gt;
I agree with chuma about forgetting VPN from a uni network.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.46552-709855</guid>
		<pubDate>Fri, 15 Sep 2006 08:27:45 -0800</pubDate>
		<dc:creator>paulsc</dc:creator>
	</item><item>
		<title>By: Leech</title>
		<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why#710091</link>	
		<description>Maybe it doesn&apos;t apply to your architecture but when I get stuck in those networking on windows, I use &lt;a href=&quot;http://www.hamachi.cc/&quot;&gt;Hamachi&lt;/a&gt; and problem solved.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.46552-710091</guid>
		<pubDate>Fri, 15 Sep 2006 11:31:46 -0800</pubDate>
		<dc:creator>Leech</dc:creator>
	</item><item>
		<title>By: criticman</title>
		<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why#710986</link>	
		<description>Client: Windows XP Pro, setup through the &quot;Create a new network connection wizard, connect to work network, VPN, etc&quot;&lt;br&gt;
Server: Windows NT&lt;br&gt;
Corporate Firewall: A Cisco device&lt;br&gt;
WRT54G: Latest firmware revision updated last week from their site</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.46552-710986</guid>
		<pubDate>Sat, 16 Sep 2006 12:26:27 -0800</pubDate>
		<dc:creator>criticman</dc:creator>
	</item><item>
		<title>By: paulsc</title>
		<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why#711564</link>	
		<description>If your servers are still Windows NT, you&apos;re probably trying to establish a VPN connection only to the corporate firewall, which you list as a Cisco device. Using the Windows VPN client, &lt;a href=&quot;http://www.windowsecurity.com/articles/NAT-Traversal-Security.html&quot;&gt;you get some default behaviors introduced with Windows XP SP2 that may be hanging you up&lt;/a&gt;. You may have better luck through your corporate site, if they can get you a copy of the Cisco VPN client, if you are actually making the VPN connection to the Cisco router.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.46552-711564</guid>
		<pubDate>Sun, 17 Sep 2006 12:09:48 -0800</pubDate>
		<dc:creator>paulsc</dc:creator>
	</item><item>
		<title>By: criticman</title>
		<link>http://ask.metafilter.com/46552/Cannot-connect-to-VPN-and-do-not-know-why#712502</link>	
		<description>The VPN connection is to the Win NT box, not the firewall.  The firewall is set to pass requests on that IP and that port to the box, where accounts are setup.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.46552-712502</guid>
		<pubDate>Mon, 18 Sep 2006 13:58:03 -0800</pubDate>
		<dc:creator>criticman</dc:creator>
	</item>
	</channel>
</rss>
