admitech
asked on
VPN issues: "A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate"
VPN literally just stopped working for all of our users. No changes that I am aware of. Simple MS VPN connection to a VPN server.
Server side error:
VPN2-112: A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.
PC/Workstation off Network connection error:
Error 619: A connection to the remote computer could not be established, so the port for this connection was closed.
Server-side:
Windows firewall and anything that could be blocking is off. I see the users hit the network via Firepower but then the "Error 619".
If I truly need to provide them with a workstation cert, how do I go about doing this and efficiently for several people.
TIA
Server side error:
VPN2-112: A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.
PC/Workstation off Network connection error:
Error 619: A connection to the remote computer could not be established, so the port for this connection was closed.
Server-side:
Windows firewall and anything that could be blocking is off. I see the users hit the network via Firepower but then the "Error 619".
If I truly need to provide them with a workstation cert, how do I go about doing this and efficiently for several people.
TIA
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Or the VPN head unit.
This is a question likely best posed to your VPN vendor.
This should be handled transparently during your VPN installation procedure + then updated periodically via normal VPN updates.
This should be handled transparently during your VPN installation procedure + then updated periodically via normal VPN updates.
ASKER
Apparently a bogus error on the server side after looking into this. After a reboot all was well.
Glad you got it resolved.
ASKER
A non-issue was found.
ASKER