Mooligan
asked on
(VPN) Error 798: A certificate could not be found that can be used with this Extensible Authentication Protocol.
This is the error I receive after creating a new VPN connection from a windows 2000 client. My VPN setup is a test environment with a windows 2003 RRAS as well as a Windows 2003 domain controller running IIS and Certificate services.
I enrolled the certificates by establishing a pptp connection and then accessing the web enrollment webpage. I used request a certificate | advanced certificate request | Create and submit a request to this CA. From in there I filled out the form ensuring to create a new key set as well as checking the box to store the certificate in the local computer certificate store and not the local user as I read this can help.
Any ideas?
Jason.
I enrolled the certificates by establishing a pptp connection and then accessing the web enrollment webpage. I used request a certificate | advanced certificate request | Create and submit a request to this CA. From in there I filled out the form ensuring to create a new key set as well as checking the box to store the certificate in the local computer certificate store and not the local user as I read this can help.
Any ideas?
Jason.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I see I see... yea. I ran into the Standalone vs. Enterprise CA issue before as well. I should have mentioned it. Thanks for the points.
This is the error I receive when I tried executing VPN exe in my Rackspace server which is used to connect to the Azure Servers.
In the VPN Logs I get Exception of type 'DotRas.RasException' was thrown.
So, while I manually execute the VPN I get the error as "A certificate could not be found that can be used with this Extensible Authentication Protocol. (Error 798)"
So I opened the mmc in Rackspace server and checked the certificates on Local computer, I can see that the
client certificate is installed on Personal - > Certificates - > AzureVPN-Client
and root certificate in Trusted root certification store - > AzureVPN-Root
In the server logs I get the below error logged :
"The initial Secure Socket Tunneling Protocol request could not be successfully sent to the server. This can be due to network connectivity issues or certificate (trust) issues. The detailed error message is provided below. Correct the problem and try again."
A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
BUT I am not sure what is causing the issue.
Kindly suggest as it was working fine couple of days before but suddenly started crashing.
In the VPN Logs I get Exception of type 'DotRas.RasException' was thrown.
So, while I manually execute the VPN I get the error as "A certificate could not be found that can be used with this Extensible Authentication Protocol. (Error 798)"
So I opened the mmc in Rackspace server and checked the certificates on Local computer, I can see that the
client certificate is installed on Personal - > Certificates - > AzureVPN-Client
and root certificate in Trusted root certification store - > AzureVPN-Root
In the server logs I get the below error logged :
"The initial Secure Socket Tunneling Protocol request could not be successfully sent to the server. This can be due to network connectivity issues or certificate (trust) issues. The detailed error message is provided below. Correct the problem and try again."
A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
BUT I am not sure what is causing the issue.
Kindly suggest as it was working fine couple of days before but suddenly started crashing.
ASKER
That one line you mentioned, where you said you don't request the same cert, that you use a user cert pointed me in the right direction. I went to try requesting a user certificate but realized I couldn't, and then realized that I had setup a standalone CA instead of enterprise. I think I did this back troubleshooting a different issue but didn't realize it could have been the source of my problem.
So summary of my fix: Uninstall certificate services, and reinstall as an Enterprise CA and then request a -USER- certificate through the web enrollment.
Thanks again.