ODBC through VPN

Hmm, I assume the mdb lies on a fileserver? Then you' ll have to add ENCRYPT-policies (or better yet one policy with a service group) for all services needed for SMB (" NETBIOS" ) which are ports 135-139 TCP/UDP and 445 TCP (not exactly, but close enough) towards the fileserver and add a mapping on the share like

net use x: \\123.123.123.123\share

This is not pretty and depending on the size of the database very slow (and error prone and risky for the integrity of the database itself). I wouldn' t do that. SQL-Servers a much nicer for VPN-access. Regards, Manuel

Thanks for the reply, I wouldn' t understand your explaination, Please tell me the steps to perform these setup Do i have to create a policy for external interface to internal interface allowing port forwording of port 445 to the fileserver. Total new to fortinet and networking. Thank you.

Hi, this is really, really, really dangerous if you are new to networking and firewalls and you should have someone in place who does know something about this topic. You may get it to work, but perhaps open to the whole world. OK, if you ignore my warnings you may want to look at this: http://kc.forticare.com/default.asp?id=688&Lang=1&SID=. You' ll need a FortiClient for this (eval available). Set the " service" in the " encrypt" -Policy to " ANY" to allow any traffic, including SMB. Use the command to map the drive (you need the ip of the fileserver) and you should be able to use the database. Have good AV in place because the VPN-client can infect the fileserver easily. Or share only the mdb-file. Good luck! Regards, Manuel Martin