Mac RDC and Windows Server 2008
by Volker Weber
Microsoft Remote Desktop does not want to connect. CoRD on the other hand does not want to print. I need both.
Any ideas?
It's not the server. This works from a Windows client. There is a leaked 2.1.2 RDC. Can any of my Microsoft buddies verify if there is an internal build?
2.1.1 is from March 2011
2.1.2 (leaked) is from September 2012
rdc_2.1.2_120917_release_enu_ship_clean_standard_retail_redlab_120917-apex-build-XS26-.dmg
I really wonder why Microsoft is not issuing a fix.
Comments
Guess they'll have a new one /w the next Office which is due some time in March or so. Haven't seen any private or public beta so far, though...
We just shipped Office 2013 (RTM was 10/11/12). I don't know what group is responsible for RDC but I'll check with some friends in Windows and see what I can dig up for you V.
Oh, 11/10/12 in European. :-p
I have two Windows 7 PCs at work. I get that exact same message, on one of those PCs, when trying to remote to one particular server [Wndows Server 2008]. On the other PC RDC to that server works fine.
Remoting to other servers [Server 2008 and 2003] from the PC with the problem also works fine. Its just the one server I can't remote to.
So the problem is not restricted to the Mac version. But it does appear to be related to a combination of RDC and server.
We had this problem several times and it could be solved most of the time cleaning the terminal server license cache on the client. The cache is located in a folder named "RDC Crucial Server Information" which is anywhere under /users/shared/.
I just verified this folder is still used in 2.1.1 and 2.1.2 in the TSClient framework.
My mistake - I was referring to the Windows version of Office. Looking into what's going on with the Mac version of Office & an update to this.
Dear VoWe,
nice to hear that - in my opinion - very political question in your blog ;-) We had lots of problems with customers using OS X 10.7 and 10.8 in combination with RDC 2.1.1. When I last downloaded the software, I realized for the first time that MS does not support those systems. This of course is ridicular, because 10.7 is now nearly 2 years old. The said version 2.1.2 which I found during searches works well. So for me too: Why does MS not offer that version or - even better - a newer one which also supports smartcards for logging in like the windows version does?
Kind regards,
Christian
Christian, Amy cannot speak for Microsoft. I have since learned that you need to call Microsoft Support for the fix. And they track how often they ship it. Of course they are lying to themselves since we pass the code on in lieu of a more recent Microsoft download.
Hi,
same problem here...where can I get the 2.1.2 Client ? On Microsoft Web is still 2.1.1...
Thx, Maik
Post a comment
Recent comments
Volker Weber on A week with the Q10 at 20:00
Volker Weber on A week with the Q10 at 01:28
Torben Volkmann on A week with the Q10 at 21:01
Oscar Toft on Barracuda Networks launches a 'Dropbox Killer' at 01:08
Frank Moser on Fifty Five at 08:46
Tim Franz on Time for a new Lumia at 10:27
Andrew Magerman on Fifty Five at 09:55
Joris Bos on Time for a new Lumia at 09:34
Bob Balaban on Fifty Five at 17:04
Felix Binsack on Hallo Samsung at 10:49
Detlev Buschkamp on Fifty Five at 15:20
Joerg Hochwald on Fifty Five at 13:09
Wolfgang Hilpert on Fifty Five at 11:21
Karsten Ernst on Fifty Five at 11:12
Dirk Steins on Fifty Five at 10:45
Hans Bornich on Fifty Five at 07:48
Volker Weber on Time for a new Lumia at 07:47
Ryan Partlow on Fifty Five at 23:49
Volker Berding on Fifty Five at 23:48
Matthias Röder on Fifty Five at 22:54
Heiko Müller on Fifty Five at 19:00
John Ash on Fifty Five at 17:19
Stefanie Wörtche on Fifty Five at 17:10
John Roling on Fifty Five at 16:52
Martin Wettstein on Fifty Five at 16:36
Click here to subscribe
