Manually resetting the permissions on files used by the RDP client may also help:īut I do still have one server exhibiting this behavior, and I've just about given up on a fix. I found these two descriptions of the problem, and in the three times I've encountered this issue, each approach helped once:įor a handful of users, doing a bit of switcheroo between the old client and the new client may help: If you do not have an application called Remote Desktop Connection in your Applications folder and your Mac OS version is lower than Mac OS 10.6.6, then you can try downloading the Remote Desktop Connectino for Mac 2.1.2 below. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. I haven't seen this problem when all the TS licenses are applied up-front when the terminal server is initially configured, so I suspect the client certificate needs to change when switching from grace-period mode to paid-licenses mode, but the change cannot be applied for some reason. , OS X Mountain Lion (10.8.4) Posted on 7:25 AM. In particular, it seems to crop up if the licensing grace period is part of the story. Depending on the steps followed when setting up the terminal server, the licensing server may not provide the Mac client with an updated client certificate, causing the Mac client to drop the connection. I suspect this is an issue between Windows 2008 R2 and the way the Mac RDP client version 2 refreshes its client certificate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |