13 Feb
2015
13 Feb
'15
7:29 a.m.
On 02/13/2015 10:18 AM, Tim Carroll wrote:
I had this same problem. Up until a week or two ago port 22 worked fine. Then internally 22 was ok but externally it failed. (connection denied error). I even called Bell but they denied changing anything. As soon as I changed everything too port 2222 it all worked fine again!
Perhaps they're blocking port 22. Try a TCP port 22 traceroute and see what happens. Try again with 2222.