This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VPN inbound thru UTM to 2012 R2 server

I am interested in allowing Windows clients to directly VPN or Direct Access to my 2012 R2 server which is on the internal network. Can anyone help me on how I would allow/direct this traffic inbound, rather than the tunnel terminate at the UTM.
I am familiar with DNAT, firewall rules etc but am not sure if letting VPN through is slightly different than the usual HTTP port 80 type stuff as it can also terminate at the firewall.
Also any big pros and cons as to which is best (tunnel into UTM or internal Server).
Thanks

This thread was automatically locked due to age.

Parents

0 agux69 over 10 years ago

Hi.

This is funny. I see lots of entries like this couple in the live firewall log:
NAT rule #1 TCP :20269 → :443
Default DROP TCP :20269→:443

And with TCP port 80 also.

Do I need to create manual firewall rules to allow TCP 80 and 443 from ANY to the internal VPN Server?

I added the 'Web surfing' protocols group to the 'VPN Extended Protocols' because I saw dropped TCP 80 and 443 packets.

Note: I will be OOF next week, so don't expect responses from me until August 10th.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 agux69 over 10 years ago

Hi.

This is funny. I see lots of entries like this couple in the live firewall log:
NAT rule #1 TCP :20269 → :443
Default DROP TCP :20269→:443

And with TCP port 80 also.

Do I need to create manual firewall rules to allow TCP 80 and 443 from ANY to the internal VPN Server?

I added the 'Web surfing' protocols group to the 'VPN Extended Protocols' because I saw dropped TCP 80 and 443 packets.

Note: I will be OOF next week, so don't expect responses from me until August 10th.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data