I have a working VPN server. My only problem with it had to do with DNS.
On my ebox, I added the DNS functionality, where the first DNS is 127.0.0.1 (at the very least, it will be a caching nameserver), the second one is 192.168.1.1 (my router) and the last one is 4.4.4.4 (Google nameserver, should something go terribly wrong).
Enable the DNS, configure it and check that it works locally.
Then I created a script named /etc/ebox/hooks/openvpn.postsetconf:
#!/bin/sh
host=`hostname -s`
host="/etc/openvpn/$host.conf"
echo "# Added by /etc/ebox/hooks/openvpn.postsetconf" >> $host
echo 'push "dhcp-option DOMAIN <my domain>"' >> $host
echo 'push "dhcp-option DNS 192.168.1.5"' >> $host
192.168.1.5 is the IP of my ebox.
With this setup, my Windows machines recognize my ebox as a DNS server and can actually behave as if they were local.
Not saying that this will solve your problem immediately, but since you seem to be stuck, I hope to help you get the things moving: (1) install DNS, (2) configure DNS properly, (3) make sure your clients receive those configurations properly.
Your client shouldn't see your LAN IPs, because it is on a different subnet.
Simplify your current setup, and you will simplify your problem.