We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda NextGen Firewall X

Instable PPTP connections

  • Type: Knowledgebase
  • Date changed: 5 months ago
Solution 00005269 

 
Scope:
This solution applies to:
- NG Firewall firmware versions 4.2.x, 5.0.x, 5.2.x
- netfence firmware versions 4.2.x

 
Symptoms:

In some cases you can observe lags of an already established PPTP connection, although the PPTP tunnel seems to be stable and established.

 

 
Solution:

If the bind-IP of the NG Firewall VPN service differs from the VPN-Point of Entry IP (IP where the PPTP clients terminate), the NG Firewall VPN service handles PPTP connections unstable.

- Do not use a Local Redirect rule to forward PPTP connections to the PPTP server IP.
- Inside the L2TP/PPTP configuration, the PPTP Bind IP has to be the IP address of the VPN Point of Entry (IP where the PPTP clients terminate)


 

Link to This Page:
https://campus.barracuda.com/solution/50160000000IKb0AAG