![]() ![]() Here is the output from the SonicWall logs (sorry about poor formatting):ġ 10:44:01.192 Info Authenticated Access User logged out xx.xx.xxx.xxx, 0, WAN, xx.xx.ca. yy.yyy.yy.yy, 0, WAN username, TCP Port: 0Ģ 10:43:56.048 Info VPN Client XAUTH Succeeded with VPN client xx.xx.xxx.xxx, xx.xx.ca. yy.yyy.yy.yy usernameģ 10:43:56.016 Info Authenticated Access VPN zone remote user login allowed xx.xx.xxx.xxx, 0, WAN, xx.xx.ca. yy.yyy.yy.yy, 0, WAN gbromley, TCP Port: 0Ĥ 10:43:56.000 Info VPN IKE IKE Responder: Aggressive Mode complete (Phase 1) xx.xx.xxx.xxx, 500, xx.xx.ca. yy.yyy.yy.yy, 500 VPN Policy: WAN GroupVPN AES-256 SHA1 DH Group 2 lifetime=28800 secsĥ 10:43:56.000 Warning VPN IKE Received unencrypted packet in crypto active state xx.xx.xxx.xxx, 500, xx.xx.ca. yy.yyy.yy.yy, 500 VPN Policy: WAN GroupVPNĦ 10:43:55.928 Info VPN IKE NAT Discovery : Peer IPSec Security Gateway doesn't support VPN NAT Traversal xx.xx.xxx.xxx, 500, xx.xx.ca. yy.yyy.yy.yy, 500 VPN Policy: WAN GroupVPNħ 10:43:55.704 Info VPN IKE IKE Responder: Received Aggressive Mode request (Phase 1) xx.xx.xxx.xxx, 500, xx.xx.ca. yy.yyy.yy.yy, 500 I've set it up and it almost works, but the user gets logged out right after XAUTH succeeds. There is a SonicWall article that points to IPSec by IPSecuritas for Mac devices. We previously had an open RDP port forwarding to our Terminal Server, but we were getting hit with random login attempts so had to shut that down (that should have been shut down ages ago, but.) I since configured a VPN on the SonicOS 4.2 firmware, and it works great with the Windows SonicWall Global VPN client. But until the new device gets here, I need to get a Doc connected to our EHR remotely. So I am upgrading a client's old SonicWall TZ 190 to a Meraki MX 65. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |