I can't connect to a Windows 2012 server at all with Cord. #44
Comments
|
That's strange. I switched to CoRD because I started using 2012 and the native client would no longer connect to it, reporting some licensing issues. Could you describe in more detail what happens when you try to connect from CoRD to 2012? Also, which version are you using? Try the master branch or this commit |
|
Absolutely nothing happens when I try to connect from Cord. The new 2012 servers are essentially dead to Cord. It doesn't even try to connect. I don't have to choose "disconnect" because they're never connected in the first place. Sorry I can't give you more detail, but, that's the extent of it. |
|
Sorry. I'm using the latest Cord, 0.5.7. |
|
The latest version from the website is not the same as the head on the Git. Maybe you could try that. Thank you. |
|
Sorry. I don't know what you mean. Where do I find this software "on the Git?" Thanks. |
|
When I go to "Cord" on this Git, I see the same version that I have listed. |
|
As a start, please open CoRD from the Terminal: or Then try to connect to a server as you normally do and post any messages from the Terminal here. |
|
I get this message: Could not connect the action openServerInTextEditor: to target of class AppController |
|
But I can go to Cord just fine from my Dock. |
|
Ok, this is just a warning message that I also get. Could you change logging level to "Debug" in CoRD Preferences? |
|
Tried that. Cord did indeed open, with the same messages, though. But, I still can't connect to my 2012 server. Nothing happens. |
|
You have turned off secure connections in 2012, correct? -nick Nick Peelman Sent from my iPhone
|
|
What do you mean? I guess I have because I've been connecting via Microsoft' RDP client. Which I hate. From: Nick Peelman <[email protected]mailto:[email protected]> You have turned off secure connections in 2012, correct? -nick Nick Peelman Sent from my iPhone
Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-24521127. |
|
From: http://cord.sf.net/support.html http://windows.microsoft.com/en-us/windows-vista/allow-someone-to-connect-to-your-computer-remotely "Allow connections from clients running older versions" or some extrapolation of that is important. Cord is based on rdesktop, which is ancient and doesn't support NLA. -nick Nick Peelman Sent from my iPhone
|
|
Yeh, I checked. Remote users are allowed to connect to our server in question here. From: Nick Peelman <[email protected]mailto:[email protected]> From: http://cord.sf.net/support.html http://windows.microsoft.com/en-us/windows-vista/allow-someone-to-connect-to-your-computer-remotely "Allow connections from clients running older versions" or some extrapolation of that is important. Cord is based on rdesktop, which is ancient and doesn't support NLA. -nick Nick Peelman Sent from my iPhone
Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-24521777. |
|
pb4072, no there is a specific setting in the group policy that allows older versions clients to connect (XP, 2000) and not just Vista/7/8. It is located in Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security as described in this article: http://technet.microsoft.com/en-us/library/cc742818.aspx |
|
You're speaking of Windows Server 2012? Thanks, |
|
Yes, please see the screenshot above. Unforunately Microsoft doesn't yet have a help article specific to 2012 on this topic (or I just couldn't find it), but instructions are essentially the same. |
|
I'm sorry to be such a pain, but, the whole interface of Server 2012 just blows me away. I don't recognize one bit of it. When it fires up, there's the Server Manager Dashboard. I don't see what you have listed above. |
|
This is not done through Server Manager (unless you configured RD Broker etc.). You should directly edit group policy. Assuming your domain controller does not enforce these settings, start C:\Windows\System32\gpedit.msc and navigate from there. |
|
OK. I connected to my server via other means. I went to the policies you describe. It's not clear at all which functions I should enable or not, so, I guessed. Here's what it looks like now. It still doesn't let Cord work, though. [cid:42DE5E7B-C192-4B06-AE58-315FD7B94AC5] From: dinvlad <[email protected]mailto:[email protected]> This is not done through Server Manager (unless you configured RD Broker etc.). You should directly edit group policy. Assuming your domain controller does not enforce these settings, start C:\Windows\System32\gpedit.msc and navigate from there. Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-24543341. |
|
Sorry, I can't see any picture. Could you drag&drop it in your comment again? |
|
This forum doesn't support screenshots. Mine is a PNG. But, even though it says below that it support PNGs, it doesn't. |
|
Sorry, what do you mean? Here, I can attach a png just fine. You can drag and drop it if you're in Safari. |
|
It simply doesn't work on the web for me. The interface doesn't allow me to put in any images at all. And, I'm on a Mac! Here it is again, for what it's worth. [cid:CB1431C8-9584-4681-A43F-CDEE7EF63036] From: dinvlad <[email protected]mailto:[email protected]> Sorry, what do you mean? Here, I can attach a png just fine. You can drag and drop it if you're in Safari. [screen shot 2013-09-16 at 4 20 52 pm]https://f.cloud.github.com/assets/137337/1158181/4063734e-1faf-11e3-96bd-043aa5e4ed0b.png Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-24598329. |
|
|
|
One of our IT administrators set us up with a Citrix solution. This allows me to get to this 2012 server. I guess I'll just use that from now on, instead of Cord. Thanks for all your help. |
|
Sure, though I noticed that your setting "Require user authentication for remote connection ..." is Enabled. To be able to connect with CoRD, you would need to disable it. |
|
I disabled that but I still can't get in with Cord. |
|
We are experiencing similar problems with Windows 2012 and CoRD. We can connect to the Windows 2012 servers when connected to the same network, using internal hostnames/IP. However when connecting using external IP, no connection is made. When using the Microsoft client we can connect to the external IP without problems. |
|
I got CoRd and the official RDP to connect to server 2012 by lowering the settings described here in regedit: http://cyberarms.net/security-insights/security-lab/important-windows-2012-remote-desktop.aspx |
|
No. Didn't work for me. I changed the registry entry in the first suggestion to 1, from 2. And, I don't even understand the second suggestion there. Why would I load an "official" RDP client? I thought that Cord took care of all that. Am I supposed to go and get the Microsoft client now? Does Cord actually need that to run? I can connect to all of my other servers fine. They're all 2003 or 2008. |
|
2012 or 2012 R2 works out from the box (Hand build) for me. Not sure if this is an isolated issue. |
|
Are you connecting directly to Win 2012 on a LAN or do you have firewalls with NAT between the server and CoRD? |
|
I'm using Jump Desktop now to connect to these servers. So, I'm OK now. Thanks. From: perkaby <[email protected]mailto:[email protected]> Are you connecting directly to Win 2012 on a LAN or do you have firewalls with NAT between the server and CoRD? Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-32828546. |
|
Hi Peter, |
|
Right. And I have no idea how it's working for him. I don't see any "require user authentication for remote connection" anywhere in the interface for Cord. From: perkaby <[email protected]mailto:[email protected]> Hi Peter, Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-32885437. |
|
Yes, I solved my problem by going to a pay-for solution. I realize that. But, I have work to do. Cheers. Peter Bailey From: perkaby <[email protected]mailto:[email protected]> Hi Peter, Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-32885437. |
|
So why are you responding? I was asking another person what he did to make it work, because I am having the same issue. Also if it is a problem with NAT:ed connections this might be a bug in CoRD that needs to be corrected. |
|
Relax, man. I'm responding to respond. No big deal. Peter Bailey From: perkaby <[email protected]mailto:[email protected]> So why are you responding? I was asking another person what he did to make it work, because I am having the same issue. Also if it is a problem with NAT:ed connections this might be a bug in CoRD that needs to be corrected. Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-32886270. |
Via a VPN tunnel, different subnet and no firewall in between the client / server. CoRD works fine on NAT with Windows 2003 but I never tried on Windows 2012. |
|
Not sure if it's related, but I was having a similar issue trying to connect to 2008 SP2 and was able to resolve it in a surprising way. I had two servers that (essentially) are the same configuration. CoRD could connect to both just a while back, but suddenly one stopped working. RDC connected fine to both. I noticed that on the one that wasn't working, CoRD was triggering a DNS lookup, but then there would be no visible network activity to the server. With the machines that did work, I saw the DNS lookup followed by an immediate attempt to connect to the server. After seeing the DNS requests, it dawned on me: I'm using IP addresses to connect I suspected something about the unnecessary DNS lookup response was causing the issue. And looking at the DNS responses for a few servers that worked and comparing it to the one that didn't, I found a telling result: Working servers:
Non-working server:
CoRD appears to be trying to connect to the reverseDNS address, which fails. Coincidentally, RDC does not issue a DNS lookup when connecting via IP. I didn't need the reverseDNS record for this particular IP so I removed it, flushed my DNS cache and waited a bit. I can now connect to both servers with CoRD. Unfortunately, I can't explain why it worked and then stopped. I can only assume that my ISP added the reverseDNS at some point, or something about CoRD in OS X Mavericks doesn't like it. In any case, it seems the fix for CoRD in my particular case is to either not do DNS lookup for IP address connections or figure out how to handle reverseDNS better. Hope this info helps someone else :) |
|
I can confirm the same situation as kiddailey reported. I tried to connect to a server via host-name and ip. My particular problem is that the lookup of the hostname returns an IP - but if I do a lookup of the IP it returns a different (unreachable) server name. This is a DNS configuration issue of course, but nonetheless it seems strange that CoRD wants to do a lookup from an IP. I worked around it by redirecting my DNS server to a public server (which cannot resolve the host name of my internal server) and then I could connect. |
|
I was able to resolve this. Right click on my computer, click properties, click on Remote Settings, in Remote tab below the radio button Allow remote connections to this computer, there is an check box option for Allow connections only from computers running Remote Desktop with Network Level Authentication, Uncheck this option and you will be able to connect to windows 2012 machine with CoRD |
|
Raj31 Solution worked out for me as well. Thanks Raj! |
|
Seconded - @Raj31 's solution works for me. CoRD does not support secure access and with the most recent versions of Window's they are enforcing this be default; breaking access.
|
I'm having to use the MS "Remote Desktop Connection." And, it's awful. On 2012 server there's no more start button at the lower left. You literally have to have a Windows key on your keyboard, which, being on a Mac, of course I don't have. My assistant found this morning that if you click, and click, and click around the upper right of the window you'll see some icons pop up at the right that show you Control Panel and other stuff. I'm in a position now where I literally cannot log out of the box because no matter how many times I click up there at the upper right, nothing happens.
Can someone tell me if Cord actually supports connecting to 2012 server? I don't want to deal with this Microsoft trash.
Thanks.
The text was updated successfully, but these errors were encountered: