This is not the first time I'm hearing of this so I did a lot of tests in an attempt to reproduce the issue. Using 0.0.0.0/0 in the "Remote IP address/Subnet mask" is not incorrect by itself, but I was able to reproduce server settings that cause the same issue as you have described.
I'm not sure at this point whether it's the exact same thing, for that I would need to see the server's config (but I assume that will be impossible). Nonetheless, I have registered the bug. I will inform as soon as I get a response from RND.