Error 691 The Remote Connection Was Denied Because The Username
Contents |
user name and password combination you provided is not recognized, or the selected authentication protocol is not permitted on the remote access server. Solution - the remote connection was denied because the username and password Connecting to VPN server configured in Windows server 2003 was not an issue till the remote connection was denied because the username and password combination Windows 8.1. Now connecting from Windows 10 client to the VPN server configured in Windows 2003 server is showing error the remote connection was denied because the username and password combination you provided " The remote connection was denied because the user name and password combination you provided is not recognized, or the selected authentication protocol is not permitted on the remote access server". After some the remote connection was denied because the user account is not authorized for remote login research I found issue with the CHAP and MS-CHAP V2 is used in VPN Server configured in Windows Server 2003 and creating a new VPN connection from Windows 10 its not using CHAP and MS-CHAP V2 protocol by default. Here is the some steps to create a new VPN connection from Windows 10 client connecting to VPN server configured in Windows Server 2003. Step 1 - Click
The Selected Authentication Protocol Is Not Permitted On The Remote Access Server
on Start - Go to Setting Step - 2 - Click on Network and Internet Step - 3 - Select VPN from the left menu and Add a connection, fill out the details like VPN Provider - Windows (built-in) put your user credential, server name and address, Keep VPN type as Automatic. Step - 4 - Select the new VPN connection created and click on Internet Option below the page as per the image Step - 5 - Go to Internet Properties page, select the VPN connection click on settings Step - 6 - From the VPN setting click on properties Step - 7 - From the VPN Properties setting Type of VPN should be Automatic then select "Allow these protocols .. MS-CHAP V2" Step - 8 - Now you can connect from Windows 10 client to VPN Server configured In Windows Server 2003. Windows 10 client by default does not use this CHAP and MS-CHAP V2 protocol setting, so you will get the above error connecting VPN to the VPN Server configured in Windows Server 2003. Hope the above steps will help resolving the issue… 🙂 22,270total views, 64views today Share this:Click to email this to a friend (Opens in
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 06:50:27 GMT by s_ac15 (squid/3.5.20)
user name and password combination you provided is not recognized, or the selected authentication protocol is not permitted on the remote access server. This worked fine when connecting from Windows XP and Windows 7, but suddenly stopped working when connecting from http://dascomputerconsultants.com/VPNErrorAnalysis.htm Windows 8 and 8.1. Why? Read on for the details, or Click Here to skip the geeky analysis stuff and jump to the answer. Click Here for Press Release Sniffing the glue that holds the internet togetherThat tag line used to be on the Ethereal download page, which is now called wireshark. Wireshark is a network sniffer - it captures the data flowing across a network and interprets it into easier to read geek speak instead of the remote hard to read network bits. Normal people plug things in and expect them to work. Engineering geeks like analyzing why things don't work and figuring out how to make them work. Fortunately for my clients, I'm the latter. Here is the error screen caught with a camera phone: If you have a propeller hat, now is the time to put it on and get the propeller spinning full speed! How it used to workSince it works on other the remote connection systems, the short distance to diagnosing the problem is often comparing what system "Works Great!" does with system "It Doesn't *&*!@#-ing Work", finding where they diverge, and using that as a pointer to further analysis. So rather than analyze one then the other, I think it will make more sense to compare them side by side. That isn't an eye chart - it is a thumbnail. Click on it and look at it full screen or scroll around while you read the analysis. The left side is the sniff that fails, the right side works. The first three packets up top on each trace are the SYN / SYN-ACK/ ACK of a TCP session establishing - 51,52,53 on the left, 30,31,32 on the right. The two traces are mostly the same, up till the highlighted in yellow on both sides. When two systems are attempting to establish a VPN tunnel between them, there is a lot of negotiation back and forth. There are different options for how to encrypt, what key lengths, how to authentcate, if we are compressing data or not, ... and two systems need to figure out how each other wants to talk in order to establish how they will interoperate. Incidently, this is a similar process when you type "https://" into your browser, but that is another story. So that first block on both sides in white backgroun