Microsoft RDC fails with Microsoft and CoRD remote desktop programs
I'm running CoRD on an assortment of Macs, all running Leopard and all up to date. On the one Aluminum iMac, it fails every time I try to run it. The black connection window appears momentarily and disappears. The console shows two entries from it on each crash. One says, "ERROR: recv: Connection reset by peer." The other says, "ERROR: send: No such file or directory." I get the same behavior in CoRD 0.4.3 (197) and 0.5.0-svn (213). Version 5 also puts two entries in the Console log saying, "Not bothering to animate."
I have tried using both over wireless and using the wired connection.
It doesn't matter if the connection is started from a saved connection or from a quick connect. It doesn't matter it it is a saved user or the guest account. It works on this machine if I boot from my Macbook Pro in target disk mode, but it never works from its own hard drive.
This machine has been entirely rebuilt since the problem started. An unrelated problem caused the logic board, screen, and video card to be replaced. I thought the problem might be related, so when it continued to have the problem, I took it back to the Apple Store. They replaced the memory, hard drive, and optical drive. The only original parts now are the case, front bezel, glass, and power supply.
This problem started the first week of April, 2008. It began by saying there was a licensing problem. There is no actual licensing problem, but several machines running CoRD do report this. On my personal machine, it is currently at 0 days remaining on the temporary license, but it still works fine. On the iMac, when it got to 0 days, it refused to connect again and started behaving like this.
Both version 1 and version 2 beta 3 of the Microsoft Remote Desktop Connection programs fail to work on this machine too. Version 2 says there was a problem with the licensing protocol. Version 1 says the connection was ended because of a network error. I have only tried using the Microsoft programs with wireless. Neither put anything in the logs when they fail.
This was crossposted to the CoRD bug report page.
I have tried using both over wireless and using the wired connection.
It doesn't matter if the connection is started from a saved connection or from a quick connect. It doesn't matter it it is a saved user or the guest account. It works on this machine if I boot from my Macbook Pro in target disk mode, but it never works from its own hard drive.
This machine has been entirely rebuilt since the problem started. An unrelated problem caused the logic board, screen, and video card to be replaced. I thought the problem might be related, so when it continued to have the problem, I took it back to the Apple Store. They replaced the memory, hard drive, and optical drive. The only original parts now are the case, front bezel, glass, and power supply.
This problem started the first week of April, 2008. It began by saying there was a licensing problem. There is no actual licensing problem, but several machines running CoRD do report this. On my personal machine, it is currently at 0 days remaining on the temporary license, but it still works fine. On the iMac, when it got to 0 days, it refused to connect again and started behaving like this.
Both version 1 and version 2 beta 3 of the Microsoft Remote Desktop Connection programs fail to work on this machine too. Version 2 says there was a problem with the licensing protocol. Version 1 says the connection was ended because of a network error. I have only tried using the Microsoft programs with wireless. Neither put anything in the logs when they fail.
This was crossposted to the CoRD bug report page.
Mid 2007 iMac7,1 2.4GHz, 1GB RAM, Mac OS X (10.5.2)