You are not logged in.
- Topics: Active | Unanswered
#1 2015-10-14 18:45:02
- mayhape
- Member
- Registered: 2015-10-09
- Posts: 8
[Solved] Updated to Arch-4.2.3-1: can't connect with xfreerdp or krdc
It seems that today's update has broken rdp security negotiation - which worked fine until now - regardless of how I try I get
[ERROR][com.freerdp.legacy] - freerdp_set_last_error 0x2000C
[ERROR][com.freerdp.legacy] - Error: protocol security negotiation or connection failure
KRDC (kdenetwork-krdc-15.08.2-1) just shows me a blue screen before displaying a message box with the same message.
Any ideas?
Last edited by mayhape (2015-10-14 21:29:31)
Offline
#2 2015-10-14 19:13:11
- arojas
- Developer
- From: Spain
- Registered: 2011-10-09
- Posts: 2,103
Re: [Solved] Updated to Arch-4.2.3-1: can't connect with xfreerdp or krdc
What is Arch-4.3.2.1?
Online
#3 2015-10-14 19:16:38
- smirky
- Member
- From: Bulgaria
- Registered: 2013-02-23
- Posts: 277
- Website
Re: [Solved] Updated to Arch-4.2.3-1: can't connect with xfreerdp or krdc
He probably misclicked and added an extra "3", so I assume he means 4.2.1, which should be the kernel.
If that's true, he should consider updating to 4.2.3 (latest) and test again. Otherwise, rollback to the last working version and confirm if it works again or not.
Personal spot :: https://www.smirky.net/ :: Try not to get lost!
Offline
#4 2015-10-14 20:19:58
- mayhape
- Member
- Registered: 2015-10-09
- Posts: 8
Re: [Solved] Updated to Arch-4.2.3-1: can't connect with xfreerdp or krdc
My bad - meant of course the latest kernel 4.2.3-1 - mistyped. No one else getting error connecting to Windows 2012/ Windows 8+ system since today's update?
[Update]
Seems the problem happens when connecting to Windows domain pcs - workgroup pcs don't exhibit the problem at all.
Last edited by mayhape (2015-10-14 20:22:39)
Offline
#5 2015-10-14 21:32:09
- mayhape
- Member
- Registered: 2015-10-09
- Posts: 8
Re: [Solved] Updated to Arch-4.2.3-1: can't connect with xfreerdp or krdc
Problem solved - was able to fire up a windows machine to compare results and it turns out that the windows machine also could not connect using rdp. After rebooting the domain machines I was able to connect once more. The problem was on my end.
Offline