search

dorianj / CoRD

CoRD is a Mac OS X remote desktop client for Microsoft Windows computers using the RDP protocol. It's easy to use, fast, and free for anyone to use or modify.
http://cord.sourceforge.net/
346 stars 135 forks source link

Cord won't run in OS X Mavericks‎ #50

Closed dilmerv closed 10 years ago

dilmerv commented 10 years ago

Currently with OS X Mavericks‎ Cord throws compilation errors on lockfocus methods, also when you try to remote in, it just shows a black screen.

dorianj commented 10 years ago

As of https://github.com/dorianj/CoRD/commit/aef69f060b98d6337f1d710cc7e355c3d310ef70 I don't see any compilation errors other than a few xib warnings. Perhaps you mean runtime warnings?

dilmerv commented 10 years ago

Correct runtime warnings try to launch it and see the warnings when you try to remote in, I get warnings and errors, but this was in a previous version, I will try your commit.

Sent from my iPhone

On Nov 5, 2013, at 7:48 PM, Dorian Johnson notifications@github.com wrote:

As of aef69f0 I don't see any compilation errors other than a few xib warnings. Perhaps you mean runtime warnings?

— Reply to this email directly or view it on GitHub.

peelman commented 10 years ago

0.5.7 works fine for me on Mavericks.

dorianj commented 10 years ago

Me too. Still got a bunch of emails when Mavericks shipped, so dunno what's up.

dilmerv commented 10 years ago

It works perfectly for me now with the latest version of cord I think I was running an older version

Sent from my iPhone

On Nov 14, 2013, at 1:23 PM, Dorian Johnson notifications@github.com wrote:

Me too. Still got a bunch of emails when Mavericks shipped, so dunno what's up.

— Reply to this email directly or view it on GitHub.

dinvlad commented 10 years ago

Works well here too

kirk-kerekes commented 10 years ago

Doesn't work for me, using 10.9 (13A603) and CORD 0.5.7 (5701), connecting to a Dell quad-core XEON running the latest 64bit Windows7 version. The configuration of the Dell did not change (other than MS updates) between when CoRD worked, and when it did not.

Downloaded+installed a new copy of CoRD just to make sure. Deleted all other instances of CoRD from my MBP.

Gets a "Connection Timed Out" error. Tried by network name and by IP address -- same result. Tried rebuilding the connection info from scratch -- same problem. Verified that the W7 Dell has the remote access set to accept any client.

The old MS "Remote Desktop Connection" app from 2010 connects just fine to the same device, using the default connection info set by CoRD. The current MS RDP app also connects, but the app's behavior makes it unusable.

Note that this is SELECTIVE, CoRD does connect to some remote clients. Most, in fact. However, most of the clients are pre-Windows7 or are Windows Server of various vintages.

It just doesn't want to connect to the one I most NEED it to connect to.

dorianj commented 10 years ago

@kirk-kerekes can you post the log messages you get while trying to connect to that server?

kirk-kerekes commented 10 years ago

Not particularly useful:

11/19/13 12:02:34.440 PM CoRD[96908]: Could not connect the action openServerInTextEditor: to target of class AppController 11/19/13 12:02:34.440 PM CoRD[96908]: Could not connect the action openServerInTextEditor: to target of class AppController

joapalmer commented 10 years ago

We're running this patch: https://github.com/jonnybergdahl/CoRD/downloads Working fine in Mavericks, if this would help anyone. Also fixes a problem with the clipboard.

mriffey commented 10 years ago

It appears that Network Level Authentication (NLA) could be the culprit. I cannot sign on to AWS VMs, nor to some higher-functioning cloud hosts, but the lower end vendor's VMs work just fine. Appears to be confirmed here: http://pc-addicts.com/3-remote-desktop-apps-for-os-x-mavericks/

richardrasu commented 10 years ago

I get 'connection timed out' errors when trying on OS X Mavericks with v0.5.7 (5701). Have also just tried the version above posted by @joapalmer above, but same response.

From the logs:

30/12/13 10:55:37.807 CoRD[34890]: Could not connect the action openServerInTextEditor: to target of class AppController
30/12/13 10:55:37.807 CoRD[34890]: Could not connect the action openServerInTextEditor: to target of class AppController
30/12/13 10:55:38.767 WindowServer[139]: disable_update_timeout: UI updates were forcibly disabled by application "CoRD" for over 1.00 seconds. Server has re-enabled them.
30/12/13 10:55:43.266 WindowServer[139]: common_reenable_update: UI updates were finally reenabled by application "CoRD" after 5.50 seconds (server forcibly re-enabled them after 1.00 seconds)
30/12/13 10:56:09.001 CoRD[34890]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
mattiasgeniar commented 10 years ago

I confirm what @richardrasu also mentions. Strangely enough, some RDP hosts keep working, some newly added ones do not. Mixed variety of Windows Server 2008 R2 and Server 2012, all have RDP access enabled etc. Works with the Remote Desktop Connection app from Microsoft on Mac, not with Cord.

peelman commented 10 years ago

The only thing I'll suggest is to double check hosts and make sure they are set to allow Non-NLA-enabled clients. You can say that "nothing has changed" on the configuration side, but I personally have experienced a Windows update re-setting that setting, so please check.

ShawnAlan commented 10 years ago

I have been running CORD for a very long time. Currently I am running it on OS X 10.9.2 (yes, 10.9.2) with great success. I do have a couple servers, 2012, but the name on the cert does not match.. so, probably related. I can not connect to, but then I use Microsofts' Remote Desktop Connection. Not as handy, but it does work and I have not, yet, dug into the issue since 90% do work.

am155 commented 10 years ago

I'm using CORD for years without any problems. Even with OSX 10.9.1 was working fine. But I think since the day I installed MIcrosofts new RDP Client CORD does't open any connection - connection timeout. MS RDP working fine. Somebody can confirm this behaviour ?

hfoffani commented 10 years ago

I have both installed and can connect with both of them from OSX Mavericks. I started to use MS client because with it I can connect using NLA hosts, which some of my customers have. That's the only problem I have with CoRD (and none of the Mavericks cases reported here.)

astuanax commented 10 years ago

I have the same problem, while running on Maverick.

The odd thing is that it solves itself with a reboot. Once the issue occurs, a black screen, all connections give me a black screen.

I am connecting to a Win7 laptop, Win2008 server (Amazon cloud), Win2012 server (a box), and they all have this problem.

This black screen can come up when I connect to one of the servers for the first time, or while I am connected to any of the servers. Once the problem occurs, all connections turn into a black screen.

Downloaded the code, and compiled the latest changes with xcode, but it seems to have the same issue. I also tried removing the plist, deleting all server, etc, nothing changed the issue.

Let me know if I can help in anyway to resolve the issue.

sairez commented 10 years ago

I'm having the same experience as @astuanax. After a reboot all my connections work fine, but if I disconnect and reconnect to a host, it comes up with a black screen. Every connection to any other host gives the black screen after that. Closing CORD and restarting it doesn't help, but rebooting my mac does.

peelman commented 10 years ago

Probably fixed in #68