Currently Being ModeratedJul 3, 2013 11:49 AM (in response to YUZA-Tom)
Currently Being ModeratedJul 7, 2013 1:47 PM (in response to cspearsall)
I figured it out. You have to create user from Profile Manager not from the the Server app. From here the options button was enabled. However, when it opended up tghe dialog box 'be changed at next login' was already unchecked. I tried logging in as this user and got the same error.
Unsupported protocol 0x8057 received
MPPE required but peer negotiation failed
Currently Being ModeratedJul 7, 2013 2:11 PM (in response to enokoner)
I got L2TP working! From my 3g iphone!
1. System Preferences ---> Network
2. Click ' +' to add a new service
3. Select Ethernet for Interface. Name it something like 'VPN Access'
4. Select a new ip in a range that will not be used by the VPN client. Server sets the range for clients above 31. I chose 25 randomly.
5. Go to the server applicatio.---> Edit under DNS Settings
6. Chane the name server to the address you chose.
7. Restart and it should work.
Currently Being ModeratedAug 8, 2013 10:37 PM (in response to YUZA-Tom)
Thank you, this solved my problem and saved me a lot of time!
But I also found, as enkoner said, that the user needed to be created in the Workgroup Manager and not in the Server App.
Currently Being ModeratedOct 14, 2013 1:02 PM (in response to YUZA-Tom)
I tried this fix along with a few others that came up when I searched for "CHAP peer authentication failed." None worked for me, but simply deleting the user account and then re-creating it did.
The user account that wasn't working had been created prior to installing Server / configuring VPN; maybe it has something to do with that. Any new accounts I create work fine but none of the old ones do.
Currently Being ModeratedOct 14, 2013 3:28 PM (in response to YUZA-Tom)
I have the same CHAP peer authentication failed. However I don't have the "options" button on the work group manager. This is only for Active Directory users. Locally created users have a different password type.
Local users have a "Shadow Password" that has "Options". The AD users all have a "Crypt Password" as shown below. How can I allow these AD users to have VPN access and authenticate correctly?
Can AD users be converted to another type of password? Can this password type work with VPN to get the CHAP authentication correct?
Currently Being ModeratedDec 1, 2013 9:46 AM (in response to YUZA-Tom)
I had the same problem... Banging my head into the wall ...
I tried everything... In the end, I deleted the OpenDirectory store in "Server App" and created a new one...
And then is was working like chame :-)
Note: The users you are adding, should MAYBE only be "Network users - service only" ...
Currently Being ModeratedDec 4, 2013 2:20 PM (in response to the_powerbart)
Thanks for the hint: "Note: The users you are adding, should MAYBE only be "Network users - service only" ...
that solved my problem. See also here at the end of video:
More Like This
- Retrieving data ...