Windows 7 failures after RDP connection

[mjb_]

We are seeing problems this morning after users of Windows 7 applied all patches.

Symptom: 

User logs into SSLVPN and clicks an RDP resource.  User receives error: dsTermServe.exe - Fatal Application Exit.

! dsTermServe.exe has exited unexpectedly.  Debug information about this issue has been created in c:\Users\<user>\AppData\Roaming\Juniper Networks\Juniper Terminal SErvice Client\dsTermServ.dmp

Error occurs on 7.1R5 and 7.4R6

Workaround:

We went through recent patches and found that after uninstalling optional patch KB2830477 users are able to connect.

We know this applies to two Win7/IE10 boxes that have all recent patches applied.  One box is a personal system and the other a very newly installed test box with no other software installed.

Is anyone else seeing a similar issue?

If so, any ideas on a better workaround that will allow the patch to be installed?

thanks

[mjb_]

http://support.microsoft.com/kb/2830477/

From the looks of this, Microsoft has added Win8.1 RDP features to Windows 7. If I understand correctly, the Juniper SSLVPN does not yet fully support Windows 8.1 RDP.

So we've been reviewing this and it appears that this could become a big issue for companies that use a lot of RDP connections. We anticipate that today and through this week many users will upgrade their Win7 machines with all updates and enable the Windows 8.1 RDP feature set.

From what I gather at http://kb.pulsesecure.net/InfoCenter/index?page=content&id=kb28018, we're out of luck until December .... is that correct?

[mtessier_]

I can confirm that KB2830477 is causing the same issue for us. We're running 7.4r4.

I see that KB2830477 can be found under the optional section of Windows Update. 

Did you have any issues resulting from uninstalling this KB? 

[C4BE_]

We have the same issue here and running 7.3R4.1.

The problem is related to the DNS subsystem. If you enter an IP in the TS profile, it connects without any problem, if you enter a DNS name you get the application fatal error.

[ITdept_]

Hi C4BE,

Thanks for that comment. Indeed entering an IP address fixes the problem. This workaround also solves the Win8.1 problems.

[stine_]

I have found that if you uninstall all juniper programs (Network Connect, Juniper Pulse, Juniper Terminal Services Client), that connecting again causes a new copy of the terminal servcies client to be installed, and this fixes the problem.

I don't know which uninstall caused the problematic program to be removed, just that after uninstalling everything, the terminal sevices client works again.

[stine_]

I just re-installed Network Connect 7.1.16 and the TS client still works.

I don't have an easy way to test a newer (from a MAG2600) client or the pulse client's impact on terminal services.

[zanyterp_]

stine: are you connecting over Pulse or through an RDP bookmark? This failure is only known to occur with RDP bookmarks/launcher using host name; direct over Pulse would be a different issue

[stine_]

The fix I found does only fix the built-in terminal services client.   My question was does the second fix work: reinstalling the juniper windows executables which doesn't require changing the bookmarks to use ip addresses.

[zanyterp_]

Thanks for clarifying, stine. The only uninstall that is known to work is the MS KB that installs the new RDP client; uninstalling Juniper components shouldn't have an impact