Is it definitely the BLAST protocol that's the issue and not RDP or PCoIP? If that's the case you'd see something like this in the agent logs:
2013-06-26T14:19:19.795+01:00 DEBUG (06A0-06F8) <Thread-39> [ComponentResponse] Message is <?xml version="1.0"?><TERMINALRESPONSE>...<PROTOCOL><NAME>RDP</NAME><PORT>3389</PORT><STATUS>ready</STATUS></PROTOCOL><PROTOCOL><NAME>PCOIP</NAME><PORT>0</PORT><STATUS>negotiate</STATUS></PROTOCOL><PROTOCOL><NAME>BLAST</NAME><PORT>0</PORT><STATUS>error</STATUS></PROTOCOL> ...
If it is, how did you install the agent? There's a known issue in the 5.2.0 agent, where if you specify an explicit list of components on the command line such as ADDLOCAL=Core,PCoIP,USB,VPA,VmwVaudio,VmVideo,VMCI then you don't get the HTML access interface dll (needed for talking to the feature pack component), causing the protocol to be reported as in an error state even if the feature pack is not installed. You can include the Appblast component in the list to work around this.