This causes me a great deal of concern since I wholly don’t expect to get the configuration working the first time over night and will need to make sure a VPN solution is operational at almost all times. It is recommended that I don’t keep the dynamic vpn configured when switching over to Juniper Secure Connect. I’ve reviewed the documentation and unfortunately it almost immediately addresses my initial concern. If Juniper is pushing their own solution then I guess that should be the selected alternative since I would expect them to phase out third party applications over time in favor of their own products. I did look at NCP at the time and while I was interested in the product, it was outside the scope of what I could take on at the time. To be fair by background is not in networking and I was learning JunOS at the same time I was trying to get this up and running. We bought our licenses for dynamic vpn at the end of and it took me a LOT of trial and error to get that working. Now that my moaning is out of the way, I can’t say I’ve stayed up on all of the latest so this is news to me. Thank you for your patience and participation. We’ve implemented full moderation to control spam. If your post is rejected, you’ll receive an email outlining the reason s. Please expect a brief delay-there is no need to post multiple times.
This community is currently under full moderation, meaning all posts will be reviewed before appearing in the community.
0 kommentar(er)
