There are several possible causes. One is that you are pointing to the wrong server, maybe the address is different to the outside or there is a gateway. Another could be that there is a firewall misconfigured to block in coming ssh connections. A third possibility is that the ssh server is listening on another port than the standard port. A fourth is that the ssh server wasn't started on that machine. Have you been able to connect to that server before via SSH on a different network?
part of the diagnosis will be the length of time it took to respond. Did this error appear in 3 seconds or less, or was it more like 40 seconds?
A quick failure suggests more that the server is not listening for you, but the messages suggest the latter which could be incorrect DNS entry, network routing or firewall issues. You need to check that the target server has a route to the source to respond with.
Another possible issue could be if the target server has multiple IP addresses and the default route doesn't know how to find the source address.
Can you get a traceroute -n ftb-dev.apj.hp to work?