Changes

From SME Server
Jump to navigationJump to search
3,355 bytes added ,  07:09, 25 May 2015
m
Line 1: Line 1: −
== Virtual Private Networking (VPN) practical tips ==
  −
  −
   
===Overview===
 
===Overview===
   Line 12: Line 9:  
http://www.domain-logic.com/support/secure_tunnel_XP.htm
 
http://www.domain-logic.com/support/secure_tunnel_XP.htm
    +
For basic troubleshooting refer to entries made in the log file /var/log/messages at the time the VPN connection was being established
 +
 +
For advanced troubleshooting techniques see http://pptpclient.sourceforge.net/howto-diagnosis.phtml
    
===Background information===
 
===Background information===
   −
VPN uses port 1723 and protocol 47.  
+
VPN uses TCP port 1723 and protocol 47 (GRE).  
    
In server & gateway mode your modem should be configured in bridged mode and automatically forwards all traffic to the server.
 
In server & gateway mode your modem should be configured in bridged mode and automatically forwards all traffic to the server.
   −
In server only mode, your router must be configured to forward port 1723 to your server and must provide full support for protocol 47. Note that protocol 47 (GRE) is not a port and therefore you cannot forward it. Not all routers support this protocol so VPN is not always possible in this network arrangement.
+
In server only mode, your router must be configured to forward TCP port 1723 to your server and must provide full support for protocol 47. Note that protocol 47 (GRE) is not a port and therefore you cannot forward it. Not all routers support this protocol so VPN is not always possible in this network arrangement. In order to make pptp type VPN connections in this network arrangement, the router specification must clearly say that it can handle passthrough pptp VPN connections. Note that the routers at both the remote and local ends of the VPN pptp connection must be able to handle pptp VPN passthrough for this scenario to work correctly. Check your router specifications carefully. Errors in your log files may indicate that one of your routers may have a problem forwarding GRE packets. If you see LCP timeout errors in your log files, there are many possible reasons. The most likely one is that a firewall somewhere between the two ends is blocking/dropping GRE packets. Some routers/gateways automatically forward GRE when required, by watching the negotiation on TCP port 1723.
 +
 
 +
 
 +
In any point to point VPN connection, there will be numerous pieces of equipment that the signal passes through eg corporate firewalls, additional routers/firewalls, software firewalls/filters etc. All these steps in the chain must support protocol 47, if any piece of equipment in the chain does not support that protocol then the VPN connection will be unsuccessful. Sometimes these matters are out of the end users control, especially in corporate situations, or home user situations where low end broadband connections are used and ISP's limit functionality.
 +
 
 +
If you have a modem and a router between your SME server and the Internet, keep in mind that you need to open TCP port 1723 on both devices, and they must both support the protocol 47 (GRE).
      Line 41: Line 46:  
For further information please also search the forums and bugzilla for numerous reports of localised and other issues using VPN
 
For further information please also search the forums and bugzilla for numerous reports of localised and other issues using VPN
    +
===Workaround for Appletalk issue===
 +
{{Note box|Support for Appletalk has been dropped from SME Server since version 8.0}}
 +
Try this workaround to resolve issues with Kernel Panic errors, Appletalk and VPN disconnection problems
 +
 +
config setprop atalk status disabled
 +
signal-event reboot
 +
 +
Refer to these bugs
 +
 +
http://bugs.contribs.org/show_bug.cgi?id=3500
 +
 +
http://bugs.contribs.org/show_bug.cgi?id=5167
 +
 +
===Mapping Ip addresses===
 +
 +
to map a user to a fixed ip address do
 +
db accounts setprop username PPTPIP xxx.xxx.xxx.xxx
 +
signal-event remoteaccess-update
 +
where xxx.xxx.xxx.xxx is a local ip
    
===Establishing connections & drive mapping===
 
===Establishing connections & drive mapping===
   −
{{Note box|The following presupposes that if VPN'ing from behind another sme server, then the IP number and name of the local sme server & the remote sme server are different.}}
+
{{Note box|The following presupposes that if VPN'ing from behind another sme server, then the IP number and name of the local sme server & the remote sme server are different ie if the local sme server's local IP is 192.168.1.1 then the remote sme server's local IP must be 192.168.2.1 etc, if the local sme server's name is server1 then the remote sme server's name must be server2 etc.}}
 +
 
    
After establishing a VPN connection with the sme server, users then need to connect to shares  
 
After establishing a VPN connection with the sme server, users then need to connect to shares  
Line 66: Line 91:  
or
 
or
 
  net use W: \\workstationIP\c
 
  net use W: \\workstationIP\c
      
===IPSec network to network VPN===
 
===IPSec network to network VPN===
Line 73: Line 97:  
http://wiki.contribs.org/Ipsec
 
http://wiki.contribs.org/Ipsec
    +
 +
===OpenVPN===
 +
 +
OpenVPN is an alternative way to provide remote access to users from home or on the road, and completely replaces the PPTP VPN which is a part of the standard SME distribution. This method may suit users who experience connection reliability issues using the standard PPTP VPN.
 +
 +
See:
 +
http://wiki.contribs.org/OpenVPN
 +
 +
http://wiki.contribs.org/OpenVPN_Bridge
 +
 +
http://wiki.contribs.org/OpenVPN_SiteToSite
 +
 +
Also see:
 +
http://www.openvpn.net
    
===Remote Desktop Protocol (RDP)===
 
===Remote Desktop Protocol (RDP)===
Line 91: Line 129:     
http://forums.contribs.org/index.php?topic=40314.0
 
http://forums.contribs.org/index.php?topic=40314.0
 +
 +
http://forums.contribs.org/index.php/topic,46817.0.html
    
https://secure.logmein.com/home.asp?lang=en
 
https://secure.logmein.com/home.asp?lang=en
Line 106: Line 146:  
http://support.microsoft.com/kb/186607
 
http://support.microsoft.com/kb/186607
   −
The following is for general reference purposes only and is not strictly applicable to SME server.
+
This generic technical troubleshooting diagnostic guide, http://pptpclient.sourceforge.net/howto-diagnosis.phtml while not sme specific, will assist to diagnose connection problems related to VPN pptp with SME server.
http://pptpclient.sourceforge.net/howto-diagnosis.phtml
+
 
 +
Windows 7 - http://windows.microsoft.com/en-us/windows7/Set-up-a-remote-connection-to-your-workplace-using-VPN
 +
 
 +
Windows 7 - http://windows.microsoft.com/en-US/windows7/Why-am-I-having-problems-with-my-VPN-connection
       
----
 
----
 
[[Category:Howto]]
 
[[Category:Howto]]
 +
[[Category:Administration:VPN]]

Navigation menu