Do you not have a firewall section for mikrotik at all?
If you want to connect to the windows server located behind the mikrotik, then we create an L2tp ipsec connection.
Good practice is use “default rules” which we supplement with a rule for 500.4500,1701 ports. We do not write this roll in the NAT section, but in “Input chain”. This is incoming traffic from outside.
/ip firewall filter
add action=accept chain=input comment=\
"defconf: accept established,related,untracked" connection-state=\
established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment=L2TP connection-state=new dst-port=\
500,1701,4500 in-interface-list=WAN protocol=udp
add action=accept chain=input comment="IKE IPSec" in-interface-list=WAN \
protocol=ipsec-esp
add action=drop chain=input comment="defconf: drop all not coming from LAN" \
in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" \
ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" \
ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" \
connection-state=established,related
add action=accept chain=forward comment=\
"defconf: accept established,related, untracked" connection-state=\
established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=\
invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" \
connection-nat-state=!dstnat connection-state=new in-interface-list=WAN
Hi,
Mikrotik is working for outside client request with both L2TP and PPTP. The issue is when we need to connect Mikrotik L2TP Client with Windows RRAS, its givin error.
Apparently, you already have one L2TP tunnel to the RRAS server via Mikrotik, and Windows won’t give you a second tunnel. Search on the topic 2 L2TP via NAT