dereli's questions

This seems to be a general problem, but I couldn't manage to solve it.

I have a very simple configuration which follows. The server is Windows Server 2003 and client is Windows 7 Ultimate. On both, OpenVPN runs as service. I patched the "IPEnableRouter" value to 1 on OpenVPN server machine.

I CAN ping and connect ports on VPNSRV, but I CAN'T connect to any port on FTPSRV from CLIENT. VPNSRV don't have any problems connecting to FTPSRV.

Verbose logging shows that OpenVPN takes packets from CLIENT then writes, but no reply returns when pinging FTPSRV. Things are fine with pinging VPNSRV

CLIENT: LAN(192.168.2.x), OPENVPN(10.10.43.x)
VPNSRV: LAN(10.10.0.3),   OPENVPN(10.10.43.1)
FTPSRV: LAN(10.10.0.6)

client.ovpn

client
proto tcp
dev tun
dev-node lanvpn
remote vpnserver 10000
resolv-retry infinite
nobind
mute-replay-warnings
ca ca.crt
ns-cert-type server
cipher BF-CBC
comp-lzo
verb 3
cert client.crt
key client.key

server.ovpn

port 10000
proto tcp
dev tun
dev-node lanvpn
ca ca.crt
cert server.crt
key server.key
crl-verify crl.pem
dh dh1024.pem
cipher BF-CBC
comp-lzo
ifconfig-pool-persist ipp.txt
server 10.10.43.0 255.255.255.0
push "route 10.10.0.0 255.255.255.0"
keepalive 30 120
status openvpn-status.log
verb 3

Since task scheduler API has been changed after Vista & Server 2008, scheduling a task with schtasks is (as much as I know) the only way that works on both Windows 2003 Server and Windows 2008 Server.

I need to create a task that will run every on 5th and 20th of each month. Is this possible with schtasks.exe?

Creating a scheduled task that will run on every sunday and monday of a week is possible with:

schtasks /create /tn test /tr "cmd.exe" /sc weekly /d mon,sun

But with the same aspect, any of the following is not working.

schtasks /create /tn test /tr "cmd.exe" /sc monthly /d 5,15

schtasks /create /tn test /tr "cmd.exe" /sc monthly /d "5 15"

Any ideas?

Is there any way to use pfsense as caching DNS server. It will resolve domains starting from root servers and will cache them for consequent hits.

I tried DNS servers package on pfsense 1.2.2, which I guess uses WAN dns serversby default.