Windows 8 Connection Warning

Topics: Developer Forum
Jul 11, 2012 at 9:42 PM

Hello,

on Windows 8 Release Preview Terminals generats on every RDP Connect a warning "A website is trying to start a remote connection".

Is any chance to supress this?

Regards

Aug 3, 2012 at 4:40 PM

I have the same problem, any solutions yet?

Aug 4, 2012 at 2:39 PM

I cannot replicate this on Windows 8 Release Preview.

Please check this page: http://social.technet.microsoft.com/wiki/contents/articles/5573.how-to-resolve-the-issue-a-website-wants-to-start-a-remote-connection-the-publisher-of-this-remote-connection-cannot-be-identified.aspx

Aug 23, 2012 at 9:21 AM

Confirm same problem on Win 8 Ent RTM (but with mRemote). If anybody will found solution please let know.

Aug 24, 2012 at 7:28 PM

I'm having the exact same problem. Not sure if this is an mRemote issue or if it's a Windows 8 RTM issue. If anyone finds a work around, please post it. 

 

Thanx. -Jim

Aug 24, 2012 at 7:45 PM

In fact I start to use mRemoteNG. It have no such "bug" with 8.

Aug 27, 2012 at 5:34 PM

chw, thanks so much for posting! Downloaded mRemoteNG and I don't get the security warning anymore. You are a rockstar! 

 

-Jim

Sep 25, 2012 at 6:41 PM

I am also having this problem on Win 8 Enterprise x64.

Oct 25, 2012 at 4:01 PM

This now happens under Windows 7 after the RDP 8.0 update.

Coordinator
Oct 26, 2012 at 8:18 PM

Did you try the the KB mentioned in this discussion?

http://terminals.codeplex.com/discussions/400631

Oct 26, 2012 at 8:47 PM

That update (KB2592687) is what "breaks" it...removing it will make the warning message go away, but also removes RDP 8.0 support.

Oct 28, 2012 at 9:32 PM

I just started getting prompted this after installing the RDP 8.0 support on Windows 7.  I guess I'll uninstall this update.  It would be nice if the update could remain (maybe an update for Terminals?).

Here's a possible fix from someone who is using the ActiveX RDP control which I think Terminals uses too.
http://social.technet.microsoft.com/Forums/en-US/w8itprosecurity/thread/1fd2f8d2-ef44-45a8-8561-7c805dfe9bb6

"... I used a different id for the control (MsTscAx.MsTscAx instead of MSRDP.MSRDP)"

Oct 28, 2012 at 9:48 PM

Indeed, it would seem that the Terminals devs need to implement the updated MsTscAx control.  People running Windows 8 are stuck, as there's no RDP 8.0 update to remove.

Coordinator
Feb 28, 2013 at 4:17 PM
Edited Feb 28, 2013 at 4:17 PM
Coordinator
Mar 3, 2013 at 10:52 PM
Hi every body.
I have happy news. Solution is implemented and is ready to be delivered with next version.
Mar 4, 2013 at 6:59 PM
Backed up folder, dropped in the new binaries and files, no more message!

HUZZAH!!!
Mar 4, 2013 at 10:52 PM
Where does one get the latest binaries? TIA
Coordinator
Mar 5, 2013 at 4:07 PM
Mar 6, 2013 at 1:40 PM
Build new source today and working fine. Great work Jiri!!
Mar 7, 2013 at 11:29 AM
Everything is working great.

Big thanks, Jiri. Your work on this project is to be commended!
Mar 27, 2013 at 6:48 PM
Awesome! thank you jharle! Of course that did it!
Apr 2, 2013 at 5:27 PM
I've downloaded Terminals.Release.3.0.0.96.zip
and unpack it in my c:\program files\terminals
but all of my connection is gone, i have some, but they are not actual
what i did wrong ?
Coordinator
Apr 2, 2013 at 6:16 PM
@emoxam: I depends from which version you upgraded. Only upgrade from latest official build are supported. Also keep in mind, that nightly builds (3.0 is not out) are only for testing purposes and we don't guarantee, that everything works.