said by Ree:
I just realized I'm running RDP on an alternate port at home though -- maybe the unknown port is being throttled by work or Rogers. I'll put it back to 3389 later and see if that changes anything.
Apparently that was it. And apparently the throttle is on Rogers' side. Just re-tested to confirm Work -> Home was still slow as shit (and it was).
Then I reconfigured Home to listen on 3389 and re-tested, and surprise surprise I got full speeds back!
So to find out who to blame, I then configured one of my VPSes to listen on the alternate port Home was previously using. Connected Work -> VPS, and all was fast.
So it seems like Work is happy to connect to an alternate port, which can only mean that Rogers is not happy to accept connections on an alternate port.
Who knows maybe Rogers thought it was malware since the port I chose wouldn't be normally used by anything legitimate, but if that's the case it would be good if they made that "feature" known!