Question : can ssh in but then can't ssh out

I can ssh to my Cisco router.  But once I am out I cannot ssh to anywhere else on the internet.  Even though I have tcp any any eq 22 in my acl.  While attempting to ssh to a destination 1.2.3.4, I appear to be sending 'administratively prohibited unreachables' to the destination and ICMP type 3 code 13 (are they the same thing?)
When I remove my acl I can ssh out.  So it seems it is something I am blocking.  I put the acl back in but this time I allow ip any from that destination 1.2.3.4.  Now I can ssh to that destination.  But I don't want to allow all IP from 1.2.3.4, I just want to be able to ssh to it.  It is as if I need something other than tcp port 22 but that doesn't make sense.
I use putty to successfully get to my router on the internet, then use router to ssh outward.  I have done the key generation, etc.  No other firwalls that I am aware of
Any help would be appreciated.

Answer : can ssh in but then can't ssh out

Hey all,

        Just to throw in my 2 cents here. Citrix and Microsoft are huge partners here. They dont compete, they go to market together. Either hypervisor will suit just fine. Citrix FULLY supports XenDesktop on Hyper-V.

        That being said, if you are purchasing XenDesktop enterprise, you actually get Essentials for Hyper-V AND essentials for XenServer included in the pricing. This is the paid for version of the XenServer hypervisor totally included for unlimited use for your entire Citrix environment.

         Citrix does indeed have a leg up from a feature standpoint compared to Hyper-V. The argument about being able to use SCVMM and everything else in the MDOP suite is almost a non point because all the Hyper-V management tools work with XenServer as well.

       Something really cool that you will ONLY get on the Hyper-V hypervisor is the ability to use the RemoteFX display protcol. Now im not saying RemoteFX is better than ICA, but I have been hearing some great things about RemoteFX over the LAN. it is not a WAN friendly protocol however.

        One other thing to mention, I do not believe Hyper-V is tuned to run Terminal Services/ XenApp environments. You may loose concurrency here. XenServer will run that workload better.

      Anyway you go, is going to be totally fine. All these great Microsoft/Citrix tools inter operate well. Microsoft has some fantastic monitoring suites that go way beyond some of the monitoring capabilities of the native Citrix tools. Citrix tools monitor Citrix tech, and do a great job at it. Microsoft monitoring tools will go way way way beyond the citrix environment.