Workaround for Juniper Network Connect prior to version 6.2R3-1 This bug is however fixed in Juniper Network Connect version 6.2R3-1 Build # 13687. Bug in Juniper Network Connect VPN ClientĮven though the route monitor process will monitor all the routes on the client PC, it will ignore route changes if the only change was the route’s metric. If a manual routing change is detected, it will immediately terminate the VPN session. A route monitor will then monitor the routes for any changes. This will cause all the traffic to pass through the VPN tunnel. The old original routes will have a route metric value bigger than 1. The new routes will have the route metric (cost of destination) value set to 1. Once the client successfully establishes a VPN session, it will add a conflicting route for all the existing routes. Read on… Juniper Network Connect and the Routing Table Updates This however requires that Split Tunneling feature to be enabled.įortunately though, there is a workaround for Split Tunneling for Juniper VPN solutions. In this way, I am able to work on the equipment, check on my company’s knowledge base site for solutions, and respond to important emails, all at the same time. As such, whenever I am on site, I always find it easier to connect to my company’s corporate network via VPN and at the same time, work on our customer equipment by connecting to their LAN switches. In the course of my work, I am often required to work on equipment located at our customer premises.
With Split Tunneling turned off, the local LAN cannot be accessed during an active VPN session. The bad thing is that the Split Tunneling option is turned off by the administrator. Juniper VPN solution is also used at my workplace for secure remote access. One such application is the Juniper Network Connect. This service is usually facilitated through a program such as VPN client software application. Split Tunneling is a networking concept which allows the user to access the corporate private network via the VPN link, and connect to the local LAN via the same or different interface.
0 kommentar(er)
