Hey,
So I have the following setup:
LAN printer on client side
thin client (the client side) with RDP connection to VM on the VPN Server
VPN Server with virtual machines
I'm trying to print from the RDP connected Thin Client. The files are NOT on the thin client itself but on the virtual machine it is connected to. Currently i am able to print but only if I disconnect the openvpn connection first. As long as i am connected to the server the printer is not found.
I managed to ping the thin client from the server but not the printer. I surfed this forum for some time now but couldn't find a working solution for me. Split tunneling isn't working because the thin client does not have iptables. It is a HP Thin Client with it's own customized linux based OS.
I'm not entirely sure but i guess the problem is the rdp connection. The files i want to print are not on the thin client but somewhere on the servers LAN. So the server needs to "know" the printer and i don't know how to achieve this. The server can ping the thin client and the thin client can ping the printer. But the connection between the server and printer is missing.
I tried so far:
- installing the LAN brother printer on the server (didn't work because the server coulnd't find the ip-address of the printer)
- adding a push route on the server and/or a route on the client like it was suggested in
this post (after that the printers ip with a "C" after it is shown in the openvpn client list of the server. but still not able to forward anything to the printer)
I guess the solution is some ip-forwarding on the Thin Client but i have no idea how to do so without ip tables.
server-conf
port 1194 #- port
proto udp #- protocol
dev tun
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
reneg-sec 0
ca /etc/openvpn/easy-rsa2/keys/ca.crt
cert /etc/openvpn/easy-rsa2/keys/server.crt
key /etc/openvpn/easy-rsa2/keys/server.key
dh /etc/openvpn/easy-rsa2/keys/dh1024.pem
plugin /usr/lib/openvpn/openvpn-auth-pam.so /etc/pam.d/login
#client-cert-not-required #- uncomment this if you only will use ca.crt
#username-as-common-name #- uncomment this too
server 10.8.0.0 255.255.255.0
push "redirect-gateway def1"
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"
keepalive 5 30
comp-lzo
persist-key
persist-tun
status 1194.log
verb 3
route 192.168.82.0 255.255.255.0
client-config-dir /etc/openvpn/ccd
openvpn client list
OpenVPN CLIENT LIST
Updated,Mon Mar 31 11:34:07 2014
Common Name,Real Address,Bytes Received,Bytes Sent,Connected Since
PPICS,82.193.240.170:36952,39701107,711682858,Mon Mar 31 08:41:49 2014
ROUTING TABLE
Virtual Address,Common Name,Real Address,Last Ref
192.168.82.0/24,PPICS,100.100.140.170:36952,Mon Mar 31 08:41:52 2014
192.168.82.35C,PPICS,100.100.140.170:36952,Mon Mar 31 11:33:12 2014
10.8.0.6,PPICS,100.100.140.170:36952,Mon Mar 31 11:34:06 2014
GLOBAL STATS
Max bcast/mcast queue length,0
END
.82.0/24 is the client side LAN
.82.35 is the printer
10.8.0.6 is the vpn ip of the thin client
At the moment I have no access to the client conf-files but i can post them in the afternoon, if so required.
I'm not an expert on this subject. So please forgive me, if there is an obvious solution. Any help is much appreciated.
Greetings
