[SOLVED] Forwarded ports errors

[gozer 0]

Hi

I am receiving errors when I try to forward ports.

It is the same errors for several weeks.

It does not work on any server.

TCP + UDP = Not reachable on server IP over the external port XXXX, tcp protocol. Error : 110 - Connection timed out

TCP = Not reachable on server IP over the external port XXXX, tcp protocol. Error : 110 - Connection timed out

UDP = DANGER! Reachable on real IP over the external port XXXX, udp protocol. (in red token)

I am only clicking the +ADD button.

I think it is not the same issue as the other thread.

Can you help?

Thx

[Staff 9972]

Hi

I am receiving errors when I try to forward ports.

It is the same errors for several weeks.

It does not work on any server.

TCP + UDP = Not reachable on server IP over the external port XXXX, tcp protocol. Error : 110 - Connection timed out

TCP = Not reachable on server IP over the external port XXXX, tcp protocol. Error : 110 - Connection timed out

UDP = DANGER! Reachable on real IP over the external port XXXX, udp protocol. (in red token)

I am only clicking the +ADD button.

I think it is not the same issue as the other thread.

Can you help?

Thx

Hello!

The ports are correctly forwarded to you by the server you're currently (at the moment of this writing) connected to.

Those error messages are normal if you open ports while you're not running the services which have to listen to those ports. When you open/close a port, you don't need to disconnect and re-connect, but you have to wait some tens of seconds to allow the server to receive and apply the changes.

About the UDP red token, please make sure that you have not forwarded on your router that port. If you are sure of that, then it's just a false positive which may occur with UDP.

If you have still issues, please do not hesitate to contact us.

Kind regards

[gozer 0]

Thanks for the quick reply!

I did not know that the services had to be running.

I am now now seeing this message:

Reachable on server IP over the external port XXXX, tcp protocol.

In Transmission however it shows that the port is closed. Is this normal?

Thanks for the help and the service!

[Staff 9972]

Thanks for the quick reply!

I did not know that the services had to be running.

I am now now seeing this message:

Reachable on server IP over the external port XXXX, tcp protocol.

In Transmission however it shows that the port is closed. Is this normal?

Thanks for the help and the service!

Hello!

Please make sure that Transmission listens to the correct port (the port number must match the remotely forwarded port number) and that this port is forwarded both for TCP and UDP (various modern p2p clients use both protocols).

Kind regards

[gozer 0]

The forwarded port is the same in Transmission as in my forwarded ports on the settings here.

I have Transmission as allowed for all connections in Little Snitch and in OSX Firewall.

Any other ideas?

Thx!

[Staff 9972]

The forwarded port is the same in Transmission as in my forwarded ports on the settings here.

I have Transmission as allowed for all connections in Little Snitch and in OSX Firewall.

Any other ideas?

Thx!

Hello!

Can you please make sure that you start Transmission AFTER you have established a VPN connection?

Also, can you please test with completely disabled LittleSnitch and firewall?

Kind regards

[gozer 0]

I am not sure why it worked this time around as I have restarted Transmission and Tunnelblick before but it IS working now.

Thank you for the help!

[Staff 9972]

I am not sure why it worked this time around as I have restarted Transmission and Tunnelblick before but it IS working now.

Thank you for the help!

Hello!

Thank you for the information, we're glad to know that the problem is solved.

Can you please tell us if you changed anything in your system?

Kind regards