I can connect to a Terminal Services server from my iMac so long as the Terminal Server is listening on port 3389. The issue that I'm having is that we don't use the default 3389 port and the only way that I know to change that from the client side is to connect via batch file using the syntax above.
- Terminal Service Client
- Mac Terminal Program
- Macbook Terminal Window
- Terminal Service Client Download
- Microsoft Terminal Service Client
- Terminal Service Client Plugin For Asa
- Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2, Windows Server 2016 You can use the Remote Desktop client for Mac to work with Windows apps, resources, and desktops from your Mac computer.
- TSclientX is a Windows Terminal Services client for Mac OS X. It appears to be a regular Mac OS application but is in fact an assembly of free software working in concert to provide similar (better?) functionality to the official Remote Desktop Connection from Microsoft.
Active5 years, 2 months ago
This is my first implementation of Remote Desktop Services/Terminal Services; we are using it as a solution for Mac clients that need to run a piece of new Windows-only software.
My question is about streamlining the user installation process. We don't have a directory service that extends to the Windows Server at present, so I need to temporarily activate these accounts with an admin-defined password, and force the user to change their password at first login.
Unfortunately, the relevant checkbox in user management does not seem to be a workable solution... the Mac client as well as the windows RDP client fail to log in.
(Perhaps I am missing something here? We only have the RD Session Host installed so far; I'm not sure what the purpose of the Gateway Server is in our implementation. Maybe one of these solve the password reset issue? I am using the new 'Microsoft Remote Desktop' client available from the App Store, but see the same behavior with the old RDC app.)
Ideally I would like the user to be able to log in with my provided credentials, and be immediately prompted with a password change dialog. I already have a batch file running at first login, and was hoping for something that could be implemented there... the farthest I've gotten is
control /name Microsoft.UserAccounts
, but I'm unable to figure out how to drill down into the 'Change your password' screen.I was also considering
net User %USERNAME% *
until I realized that has to be run as Admin, which the batch file is not.![Juniper terminal service client download Juniper terminal service client download](/uploads/1/2/6/1/126156132/320820052.png)
It's almost certainly going to be difficult to extricate myself from the client setup process in the first place, so one final alternative I've been considering is to randomly generate secure passwords on my own, and save the user's to his or her OS X Keychain when I install -- effectively making the server login transparent.
Any wisdom from more experienced admins about how I should go about this?
NReilinghNReilingh21633 gold badges66 silver badges2222 bronze badges
1 Answer
Terminal Service Client
The only thing here preventing the 'automated' password change is the requirement for Network-Level Authentication. As long as the Remote Desktop server allows connections without NLA, the password changing functionality will work fine in either the Mac or Windows clients.
The client can still connect using NLA once the password has been changed, but the password change itself requires that a session begin without having been authenticated--NLA takes place before the session begins, and must use a valid login. Logins marked 'User must change password at next logon' are considered expired, i.e. not valid, so they cannot be used to Network-Level Authenticate a session.
To allow non-NLA sessions, open RD Session Host Configuration and double-click the RDP-Tcp connection. The checkbox for NLA is in the security Section of the General tab.
NReilinghNReilingh21633 gold badges66 silver badges2222 bronze badges
Not the answer you're looking for? Browse other questions tagged windows-server-2008-r2mac-osxpasswordremote-desktop-serviceswindows-terminal-services or ask your own question.
Active6 years, 7 months ago
I have the problem that I cannot connect to a Windows 2008 R2 (SP1) server via RDP using my Mac. The error Message I get is the following: “You were disconnected from the Windows-based computer because of problems during the licensing protocol”
From asking Mr. Google I tried the proposed solution to delete some cached files, but it didn’t resolve the problem.
The strange thing is that to other Sservers running Windows 2008 R2 (SP1) on the same Network I can connect.
I checked the configuration on the server and noticed that under Roles -> Remote Desktop Services -> RD Session Host Configuration it says under Connection Type: “Microsoft RDP 7.1”. On other server where I can connect it says “Microsoft RDP 6.1”.
Mac Terminal Program
Could that be the reason?
The Mac I use has Lion 10.7.3 installed
Bye,Martin
sysadmin1138Macbook Terminal Window
♦119k1717 gold badges151151 silver badges284284 bronze badges
mazebuhumazebuhu
3 Answers
Terminal Service Client Download
This is a known issue. You will have to wait for the hotfix from either MS or apple. Use CORD the open source RDP client. I manage several terminal servers and some macs cannot connect. MS has acknowledged the issue.
stevesteve
Use the latest rdp client 2.1.2
minazminaz
Sorry - have this Trouble today RPD 7.1 in a full patched 2008R2 Serveran NO official RDC Pack higher than 2.1.1
So you can use CoRD (http://cord.sourceforge.net/)We´ve tried and it worked fine for 'normal' user RDP Connection
Microsoft Terminal Service Client
![Windows Terminal Service Client For Mac Windows Terminal Service Client For Mac](/uploads/1/2/6/1/126156132/690708077.png)
Terminal Service Client Plugin For Asa
Greetings from Hamburg/GermanyLutz
Lutz RaheLutz Rahe