This is what I pulled out of the PCOIP log. Anything stick out that might be doing this? I'm personally thinking that it is the thin client that is doing it for whatever reason.
01/23/2013, 13:02:58.481> LVL:2 RC: 0 AGENT :MBX_CON_CLOSED
01/23/2013, 13:02:58.481> LVL:2 RC: 0 AGENT :tera_agent_disconnect: agent close code: 3, disconnect reason: 0
01/23/2013, 13:02:58.590> LVL:2 RC: 0 AGENT :tera_agent_disconnect: connection_closed 3
01/23/2013, 13:02:59.074> LVL:2 RC: 0 AGENT :monitor thread: exiting
01/23/2013, 13:04:36.402> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req
01/23/2013, 13:04:36.402> LVL:2 RC: 0 AGENT :Client address is 0.0.0.0:0 (host order)
01/23/2013, 13:04:36.402> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: For Soft Host: Using Version 1 Tag
01/23/2013, 13:04:36.402> LVL:2 RC: 0 PRI :pcoip_agent_connect_req: Session ID Tag for Soft Host: IWqSW5Yw6Zag
01/23/2013, 13:04:36.402> LVL:2 RC: 0 AGENT :server_listen_on_addr is 10.34.64.251:0 (host order)
01/23/2013, 13:04:36.402> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: Session ID = 3