topic Re: L2TP Port 1701 'filtered/closed' and unable to open! in Full Fibre

L2TP Port 1701 'filtered/closed' and unable to open!

FoolishlyWise — Wed, 07 Jun 2017 23:29:37 GMT

Slight problem with a TCP port - 1701, for use with L2TP. Tying to set up a VPN using Server 2016 Remote Access feature. It's not going well.

Quite literally, I'm finding it impossible to open the above port. Plusnet firewall is OFF, I've tried with both my pfSense router and a Netgear WNDR4000. Both have the necessary options to allow the port to be free but nope. Nothing. Interestingly, forwarding the Microsoft AD port (445) all works fine. Along with 25 (mail) etc etc. Checking on yougotsignal shows it firmly closed.

Has Plusnet recently blocked this port off?

Re: L2TP Port 1701 'filtered/closed' and unable to open!

MisterW — Thu, 08 Jun 2017 07:52:36 GMT

I don't believe that PN block any ports if the Firewall is set to OFF. However, was it already off or did you have to change it to OFF ? Any change is firewall setting will not take effect until you drop & re-establish the PPPoE connection.

Re: L2TP Port 1701 'filtered/closed' and unable to open!

mssystems — Thu, 08 Jun 2017 08:26:08 GMT

@FoolishlyWise wrote:

Slight problem with a TCP port - 1701, for use with L2TP. Tying to set up a VPN using Server 2016 Remote Access feature. It's not going well.

Quite literally, I'm finding it impossible to open the above port.

You are absolutely sure the problem is a blocked port?

L2TP requires AH and ESP to traverse the firewall; IP protocol #50 and #51 respectively. Note: protocol numbers, nothing to do with port forwarding.

Re: L2TP Port 1701 'filtered/closed' and unable to open!

FoolishlyWise — Thu, 08 Jun 2017 09:16:41 GMT

Seems like it - forwarding port 1701 (even if it was for use for another application or anything) shows it closed, even when setting it up using the most simple router or by pfSense. Haven't got onto setting IPP yet - was trying to get TCP 1701 and UDP 500 working first (the latter seems fine).

Re: L2TP Port 1701 'filtered/closed' and unable to open!

npr — Thu, 08 Jun 2017 16:22:21 GMT

Are you sure that there's a server running on the target machine port 1701 ?
If not then the test at "yougotsignal" may not be reliable.

Downloading the port checking tool at portforward.com is a more reliable test.
https://portforward.com/help/portcheck.htm

Re: L2TP Port 1701 'filtered/closed' and unable to open!

mssystems — Fri, 09 Jun 2017 06:58:03 GMT

Downloading the port checking tool at portforward.com is a more reliable test.

Or, if you use a proper operating system [sic]

# nc -l 1701

Re: L2TP Port 1701 'filtered/closed' and unable to open!

npr — Fri, 09 Jun 2017 16:56:45 GMT

Thanks, never though of using netcat for this.

nc -l -p 1701

Works well on my windows 10 machine