Mix of site to site and client-server issues

bowvalleytechnologies

Hopefully someone can provide some suggestions on where to look to fix this issue. Heres my setup:

Site #1:
DLink router at 192.168.0.1 providing DHCP to this site, forwarding port 11940 to 192.168.0.9
Windows XP with OpenVPN server running at 192.168.0.9 in bridged mode on UDP 11940
Bridge configured between the TAP adapter and second ethernet adapter at 192.168.0.68

Site #2:
Dlink router at 192.168.0.254 providing DHCP to this site
Windows XP with OpenVPN client running on 192.168.0.14
Bridge configured between the TAP adapter and second ethernet adapter at 192.168.0.15

Client #3:
Windows XP on a standalone laptop with OpenVPN client running at 192.168.0.240 (IP specified in the .ovpn file)

The issue:

Currently everything works great between Site #1 and #2, and when #3 connects it can access every device at Site #1 without issue. Browsing the workgroup (which is common to all computers) on #3 lists all devices in both Site #1 and Site #2, but nothing at #2 can be accessed from #3.

Client #3 can't easily add a second NIC so bridging it in the same way is out, so I'm starting to think the solution might be to setup a second non-bridged server at site #1 and try to connect to that instead. Would this theoretically work and make the device show up on the network so it can be accessed like any computer at #1 or #2?

Thoughts?

bowvalleytechnologies

And here are the config's:

Site #1:
local 192.168.0.9
port 11940
dev tap
secret key.txt
persist-key
persist-tun
ping-timer-rem
ping-restart 60
ping 10
comp-lzo
user nobody
group nobody
verb 3
mute-replay-warnings
replay-window 2048

Site #2:
remote XXXXXXX.gotdns.com
local 192.168.0.14
port 11940
dev tap
ifconfig 192.168.0.15 255.255.255.0
ifconfig-nowarn
secret key.txt
ping 10
comp-lzo
verb 3
replay-window 2048 15

Client #3:
remote XXXXXXX.gotdns.com
local 192.168.0.14
port 11940
dev tap
ifconfig 192.168.0.240 255.255.255.0
ifconfig-nowarn
secret key.txt
ping 10
comp-lzo
verb 3
replay-window 2048 15

janjust

interesting setup, and I'm surprised that it actually works 😉 - bridging both client and server sides is tricky, very tricky.

The client #3 setup lists

local 192.168.0.14
port 11940
dev tap
ifconfig 192.168.0.240 255.255.255.0

the 'local' does not seem right - try removing it.

also, I'm not surprised that browsing works, as domain browsers on both ends will be in sync, eventually.
The big question is , how will both LANs know where to find client #3 ?