@User are you running 0.9 or 0.8.5? We discovered this issue in 0.8.5 and the solution was to add a route rule, which should now be in windows for 0.9.