I have been writing email back and forth to germany for weeks. I could not get this software to work with a sonicwall 2040. Followed instructions, made changes.
I am not new to VPN technology, I have been designing networks for nearly 15 years, most of them secure, or encrypted.

Here is he deal... VPN Tracker works perfectly when the "DEFAULT GLOBAL VPN" is configured as indicated in the documentation with standard FQDN matching, etc.

However, most of the office uses the safenet windows client. For windows, there are two clients out there. Cisco's, and Safenet's rebranded for everyone else from Netgear to Netscreen (now Juniper).

I even tried configuring a global VPN endpoint on a different IP address than the default in the WAN IP interface, added the proper NAT rules, with NAT-T
support. No difference.

If I wipe the Sonicwall 2040 however, and move the configuration to the "Default Global VPN", it works like a charm.

So if you have a company with Sonicwall 2040's, (a very popular device) you had better have one for MAC's and another for PC's.

Sadly a convert from a Linux background and Windows for day to day, I converted to Mac book Pro as I can run X-server, have access to a Linux OS (Darwin), Can run WIN Xp on Parallels faster than in native, and Cocco for productivity. I have been able to move all applications to Max OS X, with only three exceptions:

An internal application that runs a thin client on Windows only.

Visio (Using omnigraffle as ConceptDrawPro VI can not read .xml visio files converted from .vsd. They broke it, and now the CA office is trying to communicate this to the office in Germany as well.
Only been 4 months since the anticipated release of version VI.

VPN software that works on a sonicwall.

I have to say not all the software is as good as the PC counter-part's as MAC is still a "user supported environment". I hope that changes. I also hope they can resolve the issue with ONLY working on Sonicwall Default VPN. Nice thing about the Safenet product, is on the Sonicwall you can generate the key for the user, they just import it. No technical stuff for the end user. Not only is this complex for a non-tech user to configure, but I am stuck as I have a lot more Windows users.

It is highly likely a contention issue. The default Group VPN does not have the FQDN config. VPN Tracker does not seem to know how to deal with this common issue sadly. I hope it can in the future.
In the mean time, since Sonicwal recommends Tracker for their MAC users, I need to bring this finding to their attention.