Error Connecting VPN from Windows 10 to Windows 2008 Server

Error Connecting VPN from Windows 10 to Windows 2008 Server

Q - I recently upgraded my machine to Windows 10.  When I tried to connect VPN to my office VPN server, which resides on a Windows 2008 server, it does not work.  I receive the following error message:

    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.

See attached sample screen below:


This worked with my older Windows OS workstation like Windows 7.  So the issue seems to be the setting of VPN on my Windows 10 machine.

A - Assuming this problem is due to the fact that you are using an older protocol when setting up your Windows 2008 VPN server, then you need to open up the VPN configuration on your Windows 10 machine through the class control panel to change the protocol.  You can do that by choosing "Change Adapter Options."  See sample screen below:


The following class control panel for Network Connections will show up. Right click on the VPN connection and choose "Properties" in the popup menu:



In the VPN Properties window, choose "Security Tab." Then choose "Allow these protocols" and check "Microsoft CHAP Version 2(MS-CHAP v2)."




EMK



    • Related Articles

    • Does Elliott Support Windows Server 2019?

      Release Date: 7/8/2019 Version: 8.5 Q: Does Elliott and PSQL support Windows Server 2019? A: We tested the latest Elliott 8.5 on server 2019 and it works. We can’t guarantee that the older Elliott versions will work with server 2019. In addition, per ...
    • Error Adding Printer Configuration After Latest Windows 10 Update

      Release Date: 12/20/2017 Q - We are receiving this error message in both 7.5 and 8.2 when trying to add a new printer configuration. The error only applies to our Windows 10 workstations. It seems this happened after the recent Windows 10 update: ...
    • EL800.EXE - Bad Image - MSVCRT20.dll Is Either Not Designed to Run on Windows or It Contains an Error

      Release Date: 05/18/2018 Q - I had not been able to run Elliott for the past two days. Each time when I run Elliott, I receive the following error: EL800.EXE - Bad Image M:\Elliott\Bin\MSVCRT20.dll is either not designed to run on Windows or it ...
    • Btrieve Error Codes 3000 - 3099

      MicroKernel Router Status Codes This section lists the status codes you can receive from the MicroKernel router, which receives requests from the Btrieve requesters and routes them to the correct version of the MicroKernel. 3000: The MicroKernel ...
    • Error 199 Operating System Error Code Lies Outside Expected Range

      Release Date: Version: 7.x & Up An Elliott reseller reported one of his users received an IO error message: Btrieve Error 199 on CPORDHDR AR Control File (32-Bit) 199 Operating System Error Code Lies Outside Expected Range with the following file IO ...