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 SSL VPN

What can I do if I am having trouble using Network Connector when my Barracuda SSL VPN is located in a public IP range?

  • Type: Knowledgebase
  • Date changed: 9 years ago

Solution #00004855

 

Scope:

Applies to all Barracuda SSL VPNs.

 

Answer:

When Network Connector publishes its routes to the client to tell it how to route data to the main LAN, then the client will lose access to the main public IP. The issue will occur when a client connects to an SSL VPN that is on a public IP. This is known to commonly happen on Windows XP clients but has been seen with some other operating systems.

 

For example, we have public IP 1.2.3.4. The client needs to be able to route to this obviously, but when the NC client starts, it gets a command to route that subnet via its virtual IP that Network Connector assigned to it. This route conflicts with the requirement for the client to be able to connect directly to this IP.

 

Barracuda Networks Technical Support can activate a workaround that will push another route which tells the client machine that for this specified public IP address ONLY to route back through the client’s default gateway and NOT the virtual IP.

 

Link to this page:

https://campus.barracuda.com/solution/50160000000IGHYAA4