 




<?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: VPN</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/vpn-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/vpn-3/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 20:11:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: robert stewart</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/vpn-3/#comment-54530</link>
		<dc:creator>robert stewart</dc:creator>
		<pubDate>Thu, 10 Jul 2008 17:34:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-54530</guid>
		<description><![CDATA[No you do not need static ip&#039;s for vpn, in fact this can be a hinderance to the end user. Most VPN&#039;s are used outisde of the network your trying to reach, if you set up a laptop for an end user so they can take it home and work, the end user will have to change this static ip when they move from network to network.
My point is that the ip they recieve at home will be a different ip than what they recieve at work. If your just talking about pc or laptop that will remain only in one location then you may get away with using a static ip, with this being said, if it is a home dsl line, you will have to ask your isp for a business class dsl line, otherwise your dsl ip address will not be static. Regular dsl recieves it&#039;s ip from a dhcp server somewhere and these ip&#039;s are not static. Your best bet is to leave all the tcp/ip properties to obtain automatically, this will allow the end user to move from network to network, then create the vpn (in XP you can do this through control panel, network connections), once the vpn is created you will then need to go into the tcp/ip properties of the vpn and configure the dns entry to the dns of the network the vpn is connecting to. You will also have to configure the firewall to allow vpn traffic.]]></description>
		<content:encoded><![CDATA[<p>No you do not need static ip&#8217;s for vpn, in fact this can be a hinderance to the end user. Most VPN&#8217;s are used outisde of the network your trying to reach, if you set up a laptop for an end user so they can take it home and work, the end user will have to change this static ip when they move from network to network.<br />
My point is that the ip they recieve at home will be a different ip than what they recieve at work. If your just talking about pc or laptop that will remain only in one location then you may get away with using a static ip, with this being said, if it is a home dsl line, you will have to ask your isp for a business class dsl line, otherwise your dsl ip address will not be static. Regular dsl recieves it&#8217;s ip from a dhcp server somewhere and these ip&#8217;s are not static. Your best bet is to leave all the tcp/ip properties to obtain automatically, this will allow the end user to move from network to network, then create the vpn (in XP you can do this through control panel, network connections), once the vpn is created you will then need to go into the tcp/ip properties of the vpn and configure the dns entry to the dns of the network the vpn is connecting to. You will also have to configure the firewall to allow vpn traffic.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/8 queries in 0.036 seconds using memcached
Object Caching 269/270 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-21 21:06:02 -->