OpenVPN Server – Manage Multiple Certificates

The same cert can be used, as long as only one connection is initiated. For Debian and most Linux distros, all files must be placed in /etc/openvpn. Place the ".key", ".crt". "ca.crt" and if your configuration specifies "ta.key", make sure you palce it there as well.

In WIN, the configuration file for your connection has the extension ".ovpn", while for debian should be renamed to ".conf"

mv ConnectionName.ovpn ConnectionName.conf

Place this file in /etc/openvpn

You will have the following files in /etc/openvpn:

ClientName.key
ClientName.crt
ca.crt
ta.key
ConnectionName.conf

If you want to have the VPN connection start at boot, uncomment AUTOSTART="all" in /etc/default/openvon

In VMware Virtual Network setting, make sure your network card is in promiscuous mode

AFAIK, the OpenVPN documentation sets you up to use a different certificate for each client. It's true that they're all signed by the same CA, but that doesn't make them all the same certificate. You should mint a new certificate for each client (otherwise revocation becomes a very unpleasant all-or-nothing proposition). Is a different certificate for each client, all signed by the same CA, not enough to do what you want?

My apologies if you already knew that OpenVPN would do this, and there are good reasons why it doesn't work for you; but your question didn't suggest that you were aware of this.