Case: accessing DVR's though OpenVPN link to Local Server

cdo

Hello, guys. Looking for direction advice :? .

Current situation:
Company's LAN includes 2 DVRs (with IPs like 192.168.1.11, 192.168.1.12).
DVRs are perfectly viewable to Local Users on the LAN.

LAN also includes a Win2003 Server Machine. Remote Clients are able to connect to it with OpenVPN and work with Remote Desktop or some .Net applications on IIS.

Through OpenVPN connection Win2003 Server Machine's IP looks like 192.168.139.100 and in LAN it is like 192.168.1.100.
So now Remote Clients cannot access or "see" LAN computers other than using Romote Desktop on Win2003 Server Machine. Which is OK for everything but viewing DVR's stream. Lets say on manager's iPad.

Our tech staff told us that since they can't install a VPN client software to our current DVRs therefore there is NO solution to access DVRs through OpenVPN connection. And we should refer to DynDNS or get Static External IP and expose DVR's to external connections. The "no solution" part sounds a bit odd to me.

Advice needed:
Basically how to do that through OpenVPN in "the least pain" manner?
I suppose that there is a plenty variety of solutions starting with Bridging Remote Clients to the LAN... ending with running Reverse Proxy on IIS. But what is the simplest way? Can't we just NAT Remote Clients to DVR's?

Thanks for advises.

maikcat

hi there,

Company's LAN includes 2 DVRs (with IPs like 192.168.1.11, 192.168.1.12).

Through OpenVPN connection Win2003 Server Machine's IP looks like 192.168.139.100 and in LAN it is like 192.168.1.100.

Our tech staff told us that since they can't install a VPN client software to our current DVRs therefore there is NO solution to access DVRs through OpenVPN connection.

i totally disagree....

if you are pushing routes to your clients for 192.168.1.0/24 network (which is very common net and this IS a disadvantage..)
and you have enabled ip forwarding on 2003 & configure routing on dvrs correctly you WILL see them from vpn clients...

please post configs if you want to help you.

Michael.

cdo

hi Michael,
thanks for your reply

maikcat wrote if you are pushing routes to your clients for 192.168.1.0/24 network (which is very common net and this IS a disadvantage..)
and you have enabled ip forwarding on 2003 & configure routing on dvrs correctly you WILL see them from vpn clients...
please post configs if you want to help you.

Michael.

1. Unfortunately to provide you with the conf I need to ask those tech guys. Right now I don't want to do that. I understand that you probably won't be able to say anything specific without detailed conf. But I need just a basic advice to start with.

2. As far as I can see Local Clients (connected to LAN) and Remote Clients (connected to Win2003Serv through OpenVPN) are on different subnets. Can port forwarding on 2003 Machine (which is connected to both subnets) be a solution?

maikcat

hi there,

1. Unfortunately to provide you with the conf I need to ask those tech guys. Right now I don't want to do that. I understand that you probably won't be able to say anything specific without detailed conf. But I need just a basic advice to start with.

suits me... 8-)

2. As far as I can see Local Clients (connected to LAN) and Remote Clients (connected to Win2003Serv through OpenVPN) are on different subnets. Can port forwarding on 2003 Machine (which is connected to both subnets) be a solution?

NAT on 2003 is something i avoid it...
plain routing is your problem , why complicating it more?

regards,

Michael.

cdo

Thanks a lot.
If I get it right configuring RRAS will do the trick. Correct?