Yes I have that option enabled, I did several tests, I placed a couple of laptops instead of the Router, started a simple web server on them and I’m able to connect without problems to the laptop from the VPN’s external address, which were connected to the same PPTP VPN server.
Thanks
I don’t know why it isn’t working…
The Public IP responds to PING.. but the Firewall only allows TCP80
So something else is responding…
It’s almost 02:00AM in Germany
I wish you the Best of Luck, Time for bed =)
Thank you very much, I really appreciate all your help.
I know it works for other brands and kind of devices, I’ll try to find another Mikrotik just in case there’s something wrong with the one I have right now.
@carcaussa,
Were you able to find a Solution to your Problem ?
Hi, thank you for the follow up, not really, I’ve been trying different things, including using SSTP instead of PPTP (in the test laptops they also work well with this type of VPN) but has not been successful yet
That’s a bummer!
The PPTP was working…
I searched online and found some Troubleshooting Tipps and Tricks
I think you are allowed multiple Clients (i think up to 10), but only one with the dedicated IP (duh!)
For diagnostic purposes,
Deactivate the VPN on all your devices (PC-App,Browser-Extentions, Phones, Tablets, etc..)
And retry the PPTP-Connection on the Mikrotik-Router.
Last time PING was working, but not comming from the Router…
Add this to your Firewall, it will return a “Icmp-port-unreachable” wenn pinged
/ip firewall filter
add action=reject chain=input protocol=icmp reject-with=icmp-port-unreachable place-before=0
Thank you for your help, this connection is dedicated to the router, I only used it in other devices to test. I believe the router is responding to pings, I added the filter rule just as you typed. I left a continuous ping to the external IP, as soon as I added it, I started to receive “Request timeout for icmp_seq x”, when I disable this rule I receive responses from the ping again.
After many experiments I finally solved it, I had to disable the Routing Mark in the IP/Routes rule that I created for the connection, I suppose that some relevant packets didn’t get mark.