It's common for networks to block 172.16.0.0/12, since it's private IP space that shouldn't be routed on the public internet.
172.65.32.248, which your system is trying to connect to, is not in that block, but is "nearby". But if your network administrator (or ISP?) is blocking it anyway (due to incorrectly putting in the IP range), that would explain why you can't connect to it.
We've seen it here a couple times before. Here's one recent example, but I know I've seen others.