On 21 June 2011 20:50, Daniel Case <danielcase10@gmail.com> wrote:

Hi Andy,
So surely it should get closed for 1720 as well? I have no firewall on
that server yet, wasn't going to set one up until I know all the
services I want are running properly, the firewall is just an extra
layer of troubleshooting.

Hi Daniel,

It's most likely that your ISP is filtering outbound port 1720/tcp to stop you using the connection for VoIP.

Do you have fully unrestricted and un-proxied outbound access? If you scan another IP (that you have permission to scan) do you get the same result? If I were in the same position I'd narrow it down by process of elimination, and then contact the service provider to confirm.

As Andy said there's nothing on the Bitfolk side of things that will interfere with 1720/tcp traffic so it's likely to be between you and it.

Hope that helps.

Martin