<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Networknet.nl Blog &#187; nat</title>
	<atom:link href="http://www.networknet.nl/apps/wp/archives/tag/nat/feed" rel="self" type="application/rss+xml" />
	<link>http://www.networknet.nl/apps/wp</link>
	<description>Stay Connected</description>
	<lastBuildDate>Sat, 04 Sep 2010 16:37:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Cisco PIX 501 and PPTP VPN server port forwarding</title>
		<link>http://www.networknet.nl/apps/wp/archives/402</link>
		<comments>http://www.networknet.nl/apps/wp/archives/402#comments</comments>
		<pubDate>Wed, 19 Mar 2008 20:26:32 +0000</pubDate>
		<dc:creator>Ivan Versluis</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[forwarding]]></category>
		<category><![CDATA[nat]]></category>
		<category><![CDATA[pix]]></category>
		<category><![CDATA[port]]></category>
		<category><![CDATA[pptp]]></category>
		<category><![CDATA[static]]></category>

		<guid isPermaLink="false">http://www.networknet.nl/apps/wp/archives/402</guid>
		<description><![CDATA[In the following example I am configuring port forwarding to a Windows Server 2003 Standard Edition PPTP VPN server. My configuration has been configured as shown in the diagram. I have a /28 network registered on the Internet and 14 public IP Addresses are available though the SDSL ISP modem. The SDSL modem is providing]]></description>
			<content:encoded><![CDATA[<p>In the following example I am configuring port forwarding to a Windows Server 2003 Standard Edition PPTP VPN server. My configuration has been configured as shown in the diagram. I have a /28 network registered on the Internet and 14 public IP Addresses are available though the SDSL ISP modem. The SDSL modem is providing these IP addresses by the internal DHCP server. For the Cisco PIX 501 firewall I am using manual assigned Public IP Address.</p>
<p><img border="0" width="299" src="http://www.networknet.nl/apps/wp/wp-content/uploads/CiscoPIX501andPPTPVPNserverportforwardin_EE11/image.png" alt="image" height="480" style="border-width: 0px" /></p>
<p>In the CLI command lines below I am configuring static NAT on a public IP Address for tcp port 1723 (pptp) and assign the private IP Address/hostname to VPN-02 which has been defined in the line &#8220;name&#8221;.</p>
<blockquote><p>fixup protocol pptp 1723</p>
<p>name 192.168.5.35 VPN-02</p>
<p>access-list outside_access_in permit tcp any host 194.0.0.2</p>
<p>access-list outside_access_in permit gre any host 194.0.0.2</p>
<p>pdm location VPN-02 255.255.255.255 inside</p>
<p>static (inside,outside) tcp 194.0.0.2 pptp VPN-02 pptp netmask 255.255.255.255 0 0</p></blockquote>
<p>What did I achieve with this configuration? After I applied this configuration I was able to connect from my Windows XP &amp; Windows Vista clients with built-in VPN client and connect using the PPTP protocol. I also used static port forwarding on tcp 1723 port and enabled the GRE IP protocol fix by using the &#8220;fixup protocol pptp 1723&#8243; command. Without the fixup for pptp protocol I was forced to translate complete internal host (VPN-02) and using all TCP ports. If you don&#8217;t apply to fixup than you probably will get eventlog message like one below.</p>
<pre class="brush: plain;">
Event Type:    Warning
Event Source:    Rasman
Event Category:    None
Event ID:    20209
Date:        3/18/2008
Time:        9:22:43 PM
User:        N/A
Computer:    VPN-02
Description:
A connection between the VPN server and the VPN client 87.0.0.1 has been established, but the VPN connection cannot be completed. The most common cause for this is that a firewall or router between the VPN server and the VPN client is not configured to allow Generic Routing Encapsulation (GRE) packets (protocol 47). Verify that the firewalls and routers between your VPN server and the Internet allow GRE packets. Make sure the firewalls and routers on the user's network are also configured to allow GRE packets. If the problem persists, have the user contact the Internet service provider (ISP) to determine whether the ISP might be blocking GRE packets.
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.networknet.nl/apps/wp/archives/402/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
