One of our spokes in our Hub/Spoke topology disconnected.  The tunnel no longer displayed in the VPN Status page of our Hub and did not show an active tunnel despite being setup the same as every other remote station we have.    The error message on the VPN Status page for this spoke stated:  VPN Registry: This WAN appliance is unable to connect to any VPN registries using outbound UDP ports  & . NAT Type: Insufficient Registry Information.  This WAN appliance has not been able to communicate with the registry   We tried turning the tunnel off and on to no avail.  I then switched from Automatic NAT traversal to manually configuring NAT Traversal with the remote station's Public IP and a random port.  It worked for approximately 12 hours before disconnecting again.  I then switched back to Automatic, and now it is up again for the time being.  None of our other spokes have experienced this issue.   Anyone experienced this issue before? If so, what was the cause?  Logs aren't showing much other than a the tunnel disconnecting.  Or if there is a particular log I should be searching for which may provide clues?   I am hoping switching back to Automatic permanently solves the issue but still monitoring.  ... View more