This happened to me when I copied my remmina configuration (under /.remmina) from one machine to another. Perhaps the remmina versions were different; changing security did not help but deleting and recreating the connection did.
remmina unable to connect to rdp server windows 2008 17
Download Zip: https://urllio.com/2vDJ7d
Probably stupid answer, but the problem for me was that I tried connecting through an open Wi-Fi network (unencrypted) and remmina wouldn't allow that. Once I connected to a secure network everything worked as planned again.
On the Windows server's remote desktop connection properties, it is set to "safer". Specifically, the selected option is "Allow connections only from computers running Remote Desktop with Network Level Authentication."
On my Ubuntu system, I tried using Remmina to connect to the Windows server. Remmina can not connect to that server with the option "Network Level Authentication" (as mentioned in the previous paragraph). The error message Remmina returns is as follows:
Remmina uses FreeRDP for RDP connections and NLA support was added to FreeRDP in version 1.0, which is available to Ubuntu 12.04 and above. If you happen to be using an earlier version of Ubuntu and cannot upgrade, here's an updated version of remmina here, although I can't vouch for its stability: freerdp-team/+archive/freerdp
A while back I completely ditched Windows on my work computer, and went to Bauer-Puntu Linux. I've tried doing in in years past, but I've always gone back to Windows for work... Until now.One of the tools I use on a daily basis to manage my Windows servers is Remmina, which is a multi-protocol remote desktop and ssh client. In general it works great, except there were a few Windows 2008 R2 servers in my environment that would not let me connect with Remmina. When I tried to connect I would get an error saying:Unable to Connect To RDP Server x.x.x.xI finally figured out a fix. Here's what you do:Right click on the problem server, and click Edit
Click on the Advanced tab
Under Security, change the drop down from Negotiate to TLS
Click Save
That's it, now you should be able to remote desktop into your Windows 2008 R2 servers in Remmina!Related articlesRemote Desktop (RDP) Hacking 101: I can see your desktop from here!R2-D2, you know better than to trust a strange computer! Why doesn't the Mac OS X RDP Client trust Windows Server 2012 R2?Unable to RDP to TMG 2010 server (0x80074e21 FWX_E_ABORTIVE_SHUTDOWN)Accelerate RDP?
All connections are in a windows domain. Have tried various O/S's; Win 7, XP, 2008 R2. Same result. Have tried RDP, TLS, NLA and Negoitate. All systems are set to allow all types of RDP traffic. Have verified that the systems are up and function from a Win7 Vbox. Tried creating a new connection, same result.
--- Overview ---I installed Precise Beta 2 (updated to most current packages as of 4/19/12) and I've been running into the same issue as described in the initial bug report. I was getting the 'Unable to connect to RDP server XXXXXX' error dialog when trying to connect my saved RDP entries. Remmina was also displaying the following messages on the command line:
For this problem I should note that I transfered my /.remmina directory from my previous Ubuntu 11.10 installation to the fresh installation of Precise Beta 2 since I had a lot of RDP entries defined. This caused a problem because Remmina can apparently store passwords for RDP entries in one of two locations: in the same file where the RDP information is stored (/.remmina/.remmina) or in the gnome keyring. Apparently in Ubuntu 11.10, the passwords for my RDP entries were being stored in the gnome keyring, but in Precise Beta 2 the package 'remmina-plugin-gnome' which gives remmina the ability to work with the gnome keyring is not installed by default. Therefore, it wasn't able to pull my password out of the keyring and failed to connect to the RDP server.
1) Remmina always fails with following errors: a) started from console/terminal (to see some additional info):myUsername@myhost:$ remminaRemmina plugin VNC (type=Protocol) registered.Remmina plugin VNCI (type=Protocol) registered.Remmina plugin RDP (type=Protocol) registered.Remmina plugin RDPF (type=File) registered.Remmina plugin RDPS (type=Preference) registered.Remmina plugin SFTP (type=Protocol) registered.Remmina plugin SSH (type=Protocol) registered.unable to connect to (null):3389Error: protocol security negotiation failure
Sorry for my mystake, but there are also uncomfortable troubleshooting:- only running Remmina from console shows little bit more informations,- on lucky by using xFreeRDP from console for troubleshooting I've found the reason of one common "Unable to connect" notification (it was changed fingerPrint of server)- debug windows doesn't function,...
Today I spent several hours on a Windows 7 box trying to work out why "Unable to connect to RDP server". Was it the Windows firewall? Was it McAfee being expired? What does the Windows event log tell us? (It tells us there's a connection, a session is started, and then it's disconnected. Nothing useful.) Was there an authentication problem? How about connecting with no user/password? Was it some obscure need-to-login-at-the-console-first session problem (as happens with SSH sometimes).
I also have this problem in xubuntu 14.04 the above patch did nothing for me. I have to remove known_hosts before every rdp windows connection (not for remote xubuntu) then it asks for a certificate OK every time. Very irritating as I manage 17 remote computers, but worse is how long it took to even find the known_hosts tweak. One windows 7 I can never connect to even after triple checking every possible cause. Please fix this soon.
Good news, the problem disappeared after upgrade to 16.04 (lots of other system bugs appeared however). Now I can reliably connect via remmina with vnc and xrdp with no tweaks at all. However it does pop up with an irritating message with every connection saying the certificate has changed and I have to click OK. But I can live with that now that everything else works on remmina.
The Remote Desktop Protocol (RDP) connection to your Windows-based Azure virtual machine (VM) can fail for various reasons, leaving you unable to access your VM. The issue can be with the Remote Desktop service on the VM, the network connection, or the Remote Desktop client on your host computer. This article guides you through some of the most common methods to resolve RDP connection issues.
When the Remote Desktop client reconnects, the RDSH server reconnects the client to a new session instead of the original session. However, when you check the RDSH server, it says that the original session is still active and didn't enter a disconnected state.
To work around this issue, you can enable the Configure keep-alive connection interval policy in the Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections group policy folder. If you enable this policy, you must enter a keep-alive interval. The keep-alive interval determines how often, in minutes, the server checks the session state.
I installed Remmina and freerdp following the wiki, and I have two Windows Server 2008 R2 installs with the remote desktop option "Only allow with Network Authentication" selected in Windows. When connecting the first time I could connect to both servers, but that only lasted one time. Now I can only connect to one of the servers, and the only thing that changed was I went home for the night, and came in the next morning.
I encountered an reproducible issue that I consider to be a bug only affecting users that use Remote Desktop (mstsc app) to connect from aWindows 10 1809 PC to a Windows Server 2019 machine. This is because the problem started only after receiving the Windows 10 1809 update on my personal computer used to connect to my server.
The problem consists of serious connection instability issues. It will be nearly inoperable, because it's hard to establish a successful connection; duration of establishing a connection will take a significant amount of time, and will most often hang for a while in the stage of 'Configuring' or 'Securing' a remote connection (progress bar), before also hanging for a while on a black screen right after the progress bar pops into full-screen connected mode. This black screen (instead of the interface visuals of your Windows Server 2019) can then either remain indefinitely, or transition into a view of your Windows Server 2019's visuals, but in a hung state: there'll be no interaction possible, and no movement of ongoing dynamically animated components (will appear like a recording/print of your Win server screen's state, so basically a frozen screen). This indicates to me that it nearly established a successfull connection, but still failed on the brink. It often spells for more success in your successive attempts.
Eventually, once you manage to successfully establish a connection, you'll be able to operate without any issues for the duration of that session. Because the difficulties to establish a connection are random, you'll end up trying to connect like 5 to 10 times, before finally, it ends up loading you into the Win server environment correctly.
My user experience is seriously impacted by this issue, since it's really hard to establish a stable connection to my Windows Server 2019 machine now. Initially, for this reason I decided to temporarily use my alternative PC (still on the Win10 1803 April version) to connect to my server, but then I went on to try to reproduce the issue and confirm it was a bug, by also updating my second PC to Win10 1809 and trying it there. The results on Win10 1809 were the same for that PC; the same type of severe connection establishment issues as my main PC encountered. After that, I switched to another network and internet line, to determine if the issues was still somehow linked to something in my own environment; it was not, the issue went on from another internet location, on both PC's. 2ff7e9595c
Comments