KB2830477 breaks RDS load balancer connections

Question

All clients worked fine prior to KB2830477. Once that patch is installed the clients are unable to connect to our load balancer from outside our office; such as from home or on the road.
Removal of that patch allows them to connect once again.
The events on the RDS load balancer show clients connecting properly. The balancer sends the redirection info back to the client.
The events on the RDS server where the client was redirected show nothing.
It's as if the latest RDC patch breaks the ability for redirection. Or, perhaps, there's a special setting on our load balancer that needs to be updated due to this new patch?
... any helpful tips?
Thanks,
Jason Morrill

Answer 1

Just some additional info regarding this problem.
These first few paragraphs represent the eventviewer entries for the failed connection coming from outside our network:
RD Connection Broker received connection request for user SOMEDOMAIN/someuser.
Hints in the RDP file (TSV URL) = tsv://MS Terminal Services Plugin.1.rdpfarm
Initial Application = 
Call came from Redirector Server = my.fqdn.org
Redirector is configured as Farm member
RD Connection Broker has successfully determined the end point for this connection request.
Endpoint name = rdpfarm
Endpoint type = Farm
Resource plugin name = MS Terminal Services Plugin
RD Connection Broker successfully processed the connection request for user SOMEDOMAIN/someuser. Redirection info:
Target Name = RDSSERVER2
Target IP Address = INSIDE_IP, OUTSIDE_IP
Target Netbios = RDSSERVER2
Target FQDN = my.fqdn.org
Disconnected Session Found = 0x0
========================
And the entries below come from the eventviewer when connecting successfully from within our intranet.
========================
RD Connection Broker received connection request for user SOMEDOMAIN/someuser.
Hints in the RDP file (TSV URL) = tsv://MS Terminal Services Plugin.1.rdpfarm
Initial Application = 
Call came from Redirector Server = my.fqdn.org
Redirector is configured as Farm member
RD Connection Broker has successfully determined the end point for this connection request.
Endpoint name = rdpfarm
Endpoint type = Farm
Resource plugin name = MS Terminal Services Plugin
RD Connection Broker successfully processed the connection request for user SOMEDOMAIN/someuser. Redirection info:
Target Name = RDSSERVER2
Target IP Address = INSIDE_IP, OUTSIDE_IP
Target Netbios = RDSSERVER2
Target FQDN = my.fqdn.org
Disconnected Session Found = 0x0
This connection request has resulted in a successful session logon (User successfully logged on to the end point). Remote Desktop Connection Broker will stop monitoring this connection request.
Session for user SOMEDOMAIN/someusersuccessfully added to RD Connection Broker's database.
Target Name = my.fqdn.org
Session ID = 2
Farm Name = rdpfarm
========================
It's almost as if something is failing and preventing a successful session logon. Like, perhaps, the updated RDC doesn't like how our internal and external IP addresses are being returned?