Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About bismarckpalm
Community Record
6
Posts
0
Kudos
0
Solutions
Badges
Oct 23 2019
6:52 AM
Unfortunately, the remote computer has not been available for further troubleshooting. I do suspect there are more issues with it other than just the VPN. However, Mac's definitely aren't my specialty. I am going to see if the user can have someone more familiar to inspect it for other problems.
... View more
Oct 16 2019
12:15 PM
I have Ping turned off but it does see the MX because I can see it trying to connect in the event logs.
... View more
Oct 16 2019
12:00 PM
The IP is the same and static and no one else is having any trouble connecting. I did try turning off the Norton firewall on the Mac but it has been in place before when this connection was working fine and turning it off had no effect. Here are some more logs that might be a clue: Non-Meraki / Client VPN negotiation msg: msg: IPsec-SA expired: ESP/Transport Non-Meraki / Client VPN negotiation msg: received broken Microsoft ID: MS NT5 ISAKMPOAKLEY Non-Meraki / Client VPN negotiation msg: ISAKMP-SA established Non-Meraki / Client VPN negotiation msg: invalid DH group 19. Non-Meraki / Client VPN negotiation msg: invalid DH group 20. Non-Meraki / Client VPN negotiation msg: received broken Microsoft ID: MS NT5 ISAKMPOAKLEY Non-Meraki / Client VPN negotiation msg: invalid DH group 19. Non-Meraki / Client VPN negotiation msg: invalid DH group 20. Non-Meraki / Client VPN negotiation msg: received broken Microsoft ID: MS NT5 ISAKMPOAKLEY Non-Meraki / Client VPN negotiation msg: phase1 negotiation failed due to time up.
... View more
Oct 16 2019
10:58 AM
Hello! I am working on an Apple computer that was connecting to my MX64 VPN successfully but suddenly stopped. The computer owner said it happened after an update. I have deleted the old VPN connection but still no luck. I also called Meraki technical support with no luck. Any ideas? On the Apple log: IPSec connection failed Error: The L2TP-VPN server did not respond. Try reconnecting. If the problem continues, verify your settings and contact your Administrator. MX64 log: msg: phase1 negotiation failed due to time up.
... View more
Apr 4 2019
7:18 AM
Thank you for the suggestions! Any thoughts on #4? Would it be too much to move the DNS and DHCP to the MX64?
... View more
Mar 28 2019
7:35 AM
Hello, I have an MX64 firewall and recently got some new Meraki MR33 access points. I am trying to configure 1 SSID for Internal and 1 for guest. My main issue is what seems to be the best / main option for the guest network is NAT mode, which uses IP addresses in the 10.0.0.0/8 range. Unfortunately, I already use 10.0.0.0 internally. My current configuration uses two VLAN’s. On one, Internal computers get DHCP from a Windows 2012 R2 server. On the other, guest computers on Wi-Fi get DHCP from the MX64 (10.0.2.0/24). I almost wish I could keep it… but I already paid for the AP’s. I also have a new Ubiquiti switch since I am out of space on the existing. I think I have a few options and would really appreciate the advice. Change internal IP addressing, using something like 10.0.2.0 internally and NAT mode for the wireless guest network – I’m afraid this would cause a lot of problems and think I would like to avoid it. Use NAT mode: Use Meraki DHCP for the guest network and hope I never have conflicts with an IP already distributed and in use internally. The 2012 server continues to be the DHCP server for internal computers. If I use this option, do you think it is best to plug the AP’s into the MX64 or my switch? Configure 2 VLANs on my switch - 1 for Wi-Fi guests, 1 for internal - use Layer 3 roaming for both the internal and guest SSID’s. I think this is similar to what I have now? Do you think I can I configure this to be as secure as the isolated 10.0.0.0/8 offered by the NAT mode? Move DHCP from Windows 2012 R2 to the MX64 and keep using the 10.0.0.0 addressing for all computers on one VLAN. I kind of like this option because of the ability to use OpenDNS, but will I run into issues with Active Directory? Other options? Hopefully that all makes sense. I would really appreciate any advice.
... View more
© 2024 Cisco Systems, Inc.
