For the past week or so I had been working with Norton support to get Norton VPN. After 'elevating' my issue twice (Level 3?), they eventually went into the registry and renamed 'DisabledComponents' to 'DisabledComponents_bkp' which is found under 'Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters'. This allowed the Norton VPN to actually turn on. I thought 'Finally!' but alas it was short lived.
Turns out that Norton VPN is fraught with issues and while free with my Norton subscription, it is absolutely NOT worth the effort. If you have it, try to turn it on. If it doesn't work right away, move on, get another VPN solution.
Once I got Norton VPN running, I then proceeded to test a few things. Could I login to other computers on my local network? No! Not a deal breaker, just turn off Norton VPN when I'm working locally, right? Wrong, upon turning off Norton VPN my network connection crashes and no obvious way to simply bring it back except for a system reboot. So maybe I can just use it when browsing the web? So I did a speed test which failed due to some crazy socket issue that I absolutely was not going to spend time trying to sort out. After that I shut Norton VPN down and rebooted.
If after multiple support chats, support calls, support 'elevations', Norton VPN still has problems then it is obviously a flawed product and should not be used or trusted to perform correctly. The need to make registry changes like the described above is another red flag indicating a product that is not ready for general use.
I hope this information will be of some use to help others avoid this annoyance.