Route subnet conflict

[illjutsu]

I have Untangle setup for server VPN on a static public IP. I download the client files for my Macbook Pro and can connect fine to everything on the other side and can also get out to the Internet. The Mac client is Viscosity.

However, when I try to connect using the Windows client, I reach everything on the other side of the VPN connection, but I can't get out to the Internet. The Windows client is Windows 7 64-Bit. I even downloaded the latest client from openvpn.net, but I get the same result.

The log for OpenVPN on Windows client says:
------------------------------
.
.
.
WARNING: potential route subnet conflict between local LAN...
.
.
.
------------------------------

The server and client LANs are on totally different subnets.
I couldn't post any IP addresses or I would get an error telling me to remove links from my post.

I already checked and only the Untangle config files and key are in the OpenVPN config folder on the Windows client. How could there be a route conflict with two different networks? Better yet, how do I fix it?

[hlarsen]

the internal network IPs are different on both sides? that error comes up when both sides of the tunnel are the same, 192.168.1.x for example.

[illjutsu]

The server LAN is 192.168.0.0|24 and the client LAN is 192.168.1.0|24. In fact, I could ping 192.168.0.1 and 192.168.0.11 (printer) on the other side, but I couldn't ping anything on the Internet. I ended up changing the client network to 192.168.50.0|24 and it worked. The only thing I can think of is the Untangle box was setup on a 192.168.1.0|24 network for testing and was then moved to the 192.168.0.0|24 network for production use. Could it be the keys need to be recreated? This is really strange.