Document ID: UG Version 1.0 of 20Ĥ 2 Introduction This guide should help to narrow down problems related to VPN connections. This documentation may not be photocopied, duplicated or translated into another language, either in part or in whole, without the previous written permission of Innominate Security Technologies AG. In addition, Innominate is neither liable for errors in this documentation nor for damage, accidental or otherwise, caused in connection with delivery, output or use of these documents.

This also applies without limitation for the implicit assurance of scalability and suitability for specific purposes.

Innominate offers no warranty for these documents. All information contained in this documentation is subject to change without previous notice. No part of this documentation may be reproduced or transmitted in any form, by any means without prior written permission of the publisher. mguard technology is protected by the German patents # and # Further national and international patent applications are pending. All other brand names or product names are trade names, service marks, trademarks, or registered trademarks of their respective owners. 1 Innominate mguard VPN Troubleshooting Guide mguard smart² mguard centerport mguard blade mguard industrial rs mguard pci mguard delta² mguard rs2000/rs4000 mguard pci² Innominate Security Technologies AG Rudower Chaussee Berlin, Germany Phone: +49 (0) Fax: +49 (0)Ģ VPN Troubleshooting Table of Contents 1 Disclaimer 3 2 Introduction 4 3 VPN connection not displayed in the IPsec Status 5 4 ISAKMP SA (Phase I) could not be established Log Example of a successfully established ISAKMP SA Init.: pending Quick Mode with w.x.y.z took too long replacing phase Resp.: No received Packet registered in the VPN Logs of the Responder Resp.: initial Main Mode message received on w.x.y.z:500 but no connection has been authorized Init.: Possible authentication failure: no acceptable response to our first encrypted message Init.: ignoring informational payload, type INVALID_ID_INFORMATION Resp.: no suitable connection for peer Resp.: Signature check (on ) failed (wrong key?) Init.: Signature Check (on ) failed (wrong key?) Init.: we require peer to have ID, but peer declares 13 5 IPSec SA (Phase II) could not be established Init.: ignoring informational payload, type NO_PROPOSAL_CHOSEN Init.: ignoring informational payload, type INVALID_ID_INFORMATION Init.: No acceptable response to our first Quick Mode message: perhaps peer likes no proposal 16 6 Clients of the remote VPN Network cannot be reached through established VPN Connection Step 1: Is the internal IP of the local mguard reachable from the internal Client? Step 2: Internal IP of the Remote mguard reachable through VPN? Step 3: Do the Packets enter the VPN and are they received on the remote Side? 18 7 Other Problems VPN connections fails after 24 hours Problems transferring huge Data 19 8 Quick Reference VPN Log Error Messages 20 Document ID: UG Version 1.0 of 20ģ 1 Disclaimer Copyright 2013 Innominate Security Technologies AG March 2013 Innominate and mguard are registered trademarks of the Innominate Security Technologies AG.

Mguard rs2000 setup without shrewsoft