I just finished a support remote connection to my computer and they were able to identify that there is a conflict between the new VPN function and the Certificates for my home server setup.
So if support asks for access to your computer, please allow them. The more information they can gather, the sooner we can get a resolution for all the different incompatibilities we are seeing.
Follow up.
Just tried the VPN and it now works again. Not sure if it was an update on my system or some update on the servers.
A Newbie summary view on "Secure VPN has experienced a connection failure. Please try again later"
Norton VPN has not been working for most posting here for about a month. There are four pages of comments on this one thread. I understand there may be other threads.
The USK "fix" has 2 kudos, the ipsec "fix" has one? With the long list of it's not working even after those were posted, it doesn't make me feel all warm and fuzzy. (And would enable IPSec passthrough create a vulnerability itself?
I believe getting more exposure to this issue beyond this forum has some merit. I think there is only one comment on Amazon reviews for this product failure. After VPN has been down for a month, perhaps additional reviews there and elsewhere is a good idea? Unless revealing your ISP is a problem, maybe reporting who your ISP is in your review could help? I got Spectrum.
Sorry, but for someone like me who knows nothing about computers or routers, none of these make any sense to me. Thanks for trying to help, I guess I just have to wait until Norton comes out with a fix for me. Otherwise, I just have to consider my money not very well spent and get something else.
I've also had the same problem since about Feb 12 exactly as described above. Secure VPN could not connect to server and TAP driver was deactivated. In two sessions with Norton Help Desk, the situation has gotten worse. After numerous removal and installs, there is no TAP driver installed. Device protection is working, but if I try to open Norton 360 or My Norton, I get a Norton Autofix error "Attention Norton 360 has encountered an error: 8504, 104". I think UDP ports are not blocked. Norton says check with ISP; ISP says all is OK, check with Norton. I'm thinking about rolling back the system to before the problem started. I'm very confused.
@ Sunil G A
As requested per private message from Sunil.
Sorry for the not working zip. the last month with Norton has been challenging since I am not an IT-Professor.
On My Lenovo PC there has been several problems with Secure VPN Version 22.20.1.69 in different ways.
My Event-id is NOT 13801 - but 20227 with two different error-codes: 87 and weeks later 828.
My first download and installation of Norton360 was on 28.12.2019 and it work until my first RasClient 29.1.2020.
When 360 later was reinstalled with NRnR the Secure VPN worked - but only until first LiveUPDATE was done.
The next following to weeks I have maybe 100 evnt-iD 20227, RasClient marked with red! - all ending with this text:
"The user SYSTEM dialed a connection named NortonSecureVpn which has failed. The error code returned on failure is 87.", but in the front they all have different CoId=
where this part {4BFB4A93-3DBE-489E-AFA7-72D029AFC24B} differs.
The last reinstallation of norton 360 programme the 8.2.2020 are still in use and Secure VPN has worked from 11.2.2020 13.41 (the USK metode uninstalling all wans).
Until the 13-02-2020 10:31:08 event-id: 20227, RasClient. The error code returned on failure is 868.
Which was fixed by choosing "the setting country" as Automatic (Denmark) not only Denmark.
Secure VPN works now thanks to @USK.
If the zip conserning evnt-iD 20227, RasClient error-code 87 still cann´t be read - please ask again.
and if you need error code 828 ask again.
To make IPSec work through your firewalls, you should open UDP port 500 and permit IP protocol numbers 50 and 51 on both inbound and outbound firewall filters.
Why does IPSec use UDP.
IPSec uses UDP to get through stupid NAT devices. What's happening here is that the actual IPSec traffic is being encapsulated in UDP (IP protocol 17). The native IPSec packet would have an IP protocol header-value of 50. Since 50 is neither UDP (17) or TCP (6), stupid NAT gateways will drop the packet rather than pass it.
Message: "Connection Error: Secure VPN has experienced a connection failure. Please try again later."
This problem can occur if the IPSec port is blocked for network communication on your computer.
Hi Michael, Glad this worked for you. I have noticed that sometimes while on WiFi the VPN disconnects me so I have to make sure the auto connect is selected. This does not happen when I am on LAN. As a fix I am using a (NETGEAR) repeater and coming in hard wire off that, it actually improved my speed and stability.
Best wishes.
Been dealing with this since the last update. Tried everyone's fixes and nothing worked. Then found this on the Norton site.
"This problem can occur if the IPSec port is blocked for network communication on your computer."
Went into my router settings and enabled IPSec passthrough. No more issues, VPN works. I'm not sure why it's worked for months with the passthrough disabled, but since the last update it appears that the passthrough must be enabled. Hope this helps.
FINALLY GOT A TECH SUPPORT PERSON WHO ACTUALLY FIXED THE PROBLEM WITH THE VPN.. IT'S FINALLY WORKING... F.Y.I. To all that's reading this there have been significant improvements to the VPN service which is all I can say at the moment because it does not work the way it use to.. My Suggestion to all who are still having this problem is to get in touch with a ADVANCED tech support person which is what I did and now my VPN is working like it use to.
I HOPE THIS HELPS EVERYONE. IT'S ALSO POSSIBLE THEY ARE WORKING ON A FIX FOR THIS, HOWEVER; I AM NOT SURE.
Thank you, this appears to have worked to correct the issue of VPN blocking this forum. Still ran into the VPN blocking the Vault from opening though, unless it is disconnected first, very strange their VPN is blocking their own features.
Stop talking nonsense. 99% of Norton users don't know what home server is and it's 99% that certificates is nothing to do with this issue.
This was mypersonal experience watching as the Norton tech removed the certificates for my server and the VPN worked as it should. Re creating the certificates by reinstalling the software to access the server blocked the VPN again.
I was not suggesting that everyone has a server at home. But as SoulAsylum notes, no two computers or users are identical. There are numerous incompatibilities that the VPN is bumping into. If you are having issues, you too can supply the logs Norton asked for. And if you are contacted, you can also participate in letting the Norton techs access your system to diagnose the issue with your system.
TheWayOfYahweh. Click the search icon in the left system tray, click the run icon at the top right of the page. In the dialog that appears type in %temp% and press ok. Delete ALL the files and folders in the temp directory thats there. Next, open the OS tree, find users. Click on Public User, then open the folders there. DELETE all the files in the public user downloads folder. Reboot and recheck. This worked for me earlier today for an issue where the VPN would block the log in to the vault which now works. I'm thinking it may help with your issue as well.