Launch Remote Desktop Connection for Mac and enter in the computer name or IP Address of the machine you want to connect to. In my tests, entering in the IP Address worked the best. Next you’re prompted to enter in your user name and password of the Windows PC, then click OK.
Note. Curious about the new releases for the macOS client?
Check out. The Mac client runs on computers running macOS 10.10 and newer. The information in this article applies primarily to the full version of the Mac client - the version available in the Mac AppStore. Test-drive new features by downloading our preview app here:.Get the Remote Desktop clientFollow these steps to get started with Remote Desktop on your Mac:. Download the Microsoft Remote Desktop client from the. (If you skip this step, you can't connect to your PC.).
Add a Remote Desktop connection or a remote resource. You use a connection to connect directly to a Windows PC and a remote resource to use a RemoteApp program, session-based desktop, or a virtual desktop published on-premises using RemoteApp and Desktop Connections. This feature is typically available in corporate environments.What about the Mac beta client?We're testing new features on our preview channel on AppCenter. Want to check it out? Go to and click Download. You don't need to create an account or sign into AppCenter to download the beta client.If you already have the client, you can check for updates to ensure you have the latest version.
In the beta client, click Microsoft Remote Desktop Beta at the top, and then click Check for updates. NoteIn order to use this feature, the administrator needs to set the appropriate settings on the server.
Hello,I use a laptop as my primary machine, but have gotten tired of unplugging and plugging in 6 USB devices every day when I come to work, so I invested in a Plugable UD-3000 dock.It works pretty well, but I've found an issue that their tech support can't seem to resolve. When I use the NIC on the Plugable, I can no longer RDP into my servers, and even using LogMeIn is impossible from my web browser! I also can't seem to get my Active Directory or Exchange Management Console to connect!I use the Remote Desktops program from the RSAT package to keep all my servers in one neat organized window. But when using the NIC on the dock, the 2008 servers prompt for my password, then disconnect after inputting it. And my Server 2003 box does not prompt for any username or password, it just disconnects immediately.When using Windows 7's Remote Desktop Connection, on my 2008 boxes, I get a prompt 'Because of an error in data encryption, this session will end.
Please try connecting to the remote computer again'. On my 2003 box, I get 'Remote Desktop can't connect to the remote computer for one of these reasons.'
Message.I've tried rebooting, logging off/on, /release /renew /flushdns, etc. All I can think of is that something is seeing my machine has a different NIC or MAC address and it's preventing me from accessing the servers via RDP.Also, after I log in, it takes a while for my mapped drives to load. It shows them disconnected at first. Once it even prompted me for my username and password.I'm on a domain, have a few things enabled via GPO, pretty much just roaming profiles and mapped drives being applied, if that helps.Thank you for your help!!! @egOAI - Tried your tip.
I was able to ping Google's DNS server consistently at 28ms for a period of about 10 minutes and had only one request time out. I also pinged an internal IP (my 2003 box) at 3ms for the same period with no time outs. However, when I ran the same ping to the IP of my DNS server (2008 Server), which is in a remote location connected via internet / SonicWall VPN, I got a few request timed out errors1-2 a minute at most. So I went back to my internal NIC to compare the results and it had roughly the same symptoms.There's not a catalog of what MAC addresses are associated with PC when you join a domain, is there?
Maybe my network is not trusting this NIC because it's MAC address has never been associated with the machine? Just trying to think outside the box! Ok, getting frustrated, ugh.@egOAI - I just used a second machine to RDP into my DC. Pulled up AD and deleted my computer from the Computers list. With the Plugable NIC being the one that's plugged in, I left the domain, rebooted my machine, and logged into the local Admin account. I then went and enabled all my network adapaters (thinking that when I join the domain, my computer provides a list of MAC address for it's NIC's maybe?), did a /release /renew /flushdns. I then verified I was pulling a good IP via DHCP, could browse the web, etc., then I went ahead and re-joined the domain.
It rejoined just fine, rebooted, took a LONG time to get to the login screen and logged in. It came back and was still listed as my domain (unauthenticated). UGH.So, I unplugged the NIC, clicked under the 'View your active networks' pane to access the network properties window, then clicked 'Merge or delete network locations', and deleted the domain 2 (unauthenticated) network location. Then plugged the network cable back into the Plugable NIC. This time the network was identified as the regular domain, and does not say unauthenticated next to it anymore. However, I still cannot RDP into my servers or use LogMeIn.@afeitguy - So far, my Exchange connects in Outlook 2010, browsing in Chrome and IE work-ish. In Chrome, I can't run a search, returns an SSL connection error.
Browsing network shares and printing works, accessing our business system (DIS Keystone) does not work. I do notice it takes longer to log in, and once it logs in, my network drives aren't connected, and it seems like it takes a little while for my internet to start working in my browsers. I can ping my servers, ping externally and internally. No, just myself with this specific NIC. I can literally just move the cord from it to my laptop's built in NIC and everything works fine. Everyone else on my network has been running fine AFAIK, no helpdesk tickets submitted IRT network connectivity related issues.There are no proxies on my network. Running MSE and all Windows Updates have been applied.
Using the latest driver package from Plugable.Seems to be there's issues with https/encrypted websites with the NIC. Can't login to my SonicWall's via my web browser either.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |