NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
paskal
Apr 03, 2017Aspirant
NETGEAR ProSafe™ Gigabit 8 Port VPN Firewall FVS318Gv2
Hello,
set up the VPN Firewall to work with Iphone. All good its working.
Now want to connect a Windows 10 Client with Windows own VPN solution.
Tried to do with L2TP without IPSEC so i changed the registrey key like discript. Also tried with L2TP IPSEC and a PSK.
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] ERROR: Failed to get matching proposal for 9x.1xx.105.92[61138].
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] ERROR: No suitable proposal found for 9x.1xx.105.92[61138].
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] WARNING: Rejected phase 1 proposal as Peer's authentication method "pre-shared key" mismatched with Local "XAuth psk server".
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] WARNING: Rejected phase 1 proposal as Peer's dh_group "2048-bit MODP group" mismatched with Local "1024-bit MODP group".
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] WARNING: Rejected phase 1 proposal as Peer's authentication method "pre-shared key" mismatched with Local "XAuth psk server".
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] WARNING: Rejected phase 1 proposal as Peer's dh_group "2048-bit MODP group" mismatched with Local "1024-bit MODP group".
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] WARNING: Rejected phase 1 proposal as Peer's authentication method "pre-shared key" mismatched with Local "XAuth psk server".
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] WARNING: Rejected phase 1 proposal as Peer's encryption type "AES-CBC" mismatched with Local "3DES-CBC".
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] ERROR: invalid DH group 19.
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] ERROR: invalid DH group 20.
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] INFO: For x1.xxx.105.92[61138], Selected NAT-T version: RFC 3947
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] INFO: Received unknown Vendor ID
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] INFO: Received unknown Vendor ID
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] INFO: Received unknown Vendor ID
Mon Apr 03 16:15:35 2017 (GMT +0200): [FVS318Gv2] [IKE] INFO: Received unknown Vendor ID
Tried both with IPSEC User and with L2TP User
Please help....
1 Reply
- train_wreckLuminary
Post screenshots of the VPN config, make sure not to show your PSK.
btw, you shouldn't have to edit the registry to make the Win10 VPN client work. There's a horribly mistaken guide that's been posted around here that says you have to, but you don't and in fact shouldn't.
I made a guide for Win10 here: https://community.netgear.com/t5/VPN-Firewalls/FVS336Gv3-L2TP-IPsec-on-Windows-10/m-p/1063257/thread-id/4362?cid=wmt_netgear_organic
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!