* N.J. Thomas <[email protected]> [2013-01-29 23:40:04-0500]: > This is almost certainly due to the perimeter firewall on my end, which > does deep packet inspection. I will follow up with the folks that admin > the device to verify.
Confirmed that this was indeed the case. The firewall appliance in question did not recognize 9279 as an authorized port. But instead of blocking it like a normal firewall, it goes one step further and inspects the connection (that's why both sides could talk to each other initially for about half a second). It didn't recognize that as an authorized protocol, and so blocked off the connection. I now have to ask if they will open it up for me, but that's another matter entirely. Thanks Colin for helping debug this. Thomas
