Remote Desktop Connection (RDC) iMac to PC server with fixed IP

I have setup my first imac and as part of this process downloaded Remote Desktop Connection for macs so that I can log onto my server at work. Problem is when I attempt to connect to my remote pc the following message appears "Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. Try connecting to the Windows-based computer, or contact our administrator"

So, what if those don't help? I've had "Always connect, even if authentication fails" selected for quite a while. It was working fine. Yesterday I installed Office 2011 (and immediately installed SP1), and now it broke my ability to connect to a Windows Server 2008 VM that definitely worked yesterday before the Office upgrade.
Anybody have a solution for this? It appears to be a bug in RDC 2.10. Thanks, Microsoft. Off to find a working RDP client for the Mac…

Similar Messages

Unable to establish Remote Desktop Connection (RDC)

Hi all,
I had activated my account for Instance of SAP Business Warehouse 7.4 SP5 incl. SAP Business Objects BI 4.1 SP2 on SAP HANA 1.0 SP7 but while trying to connect using remote desktop connection, I am unable to connect. Its throwing up the error, "Remote desktop can't connect to the remote computer for one of these reasons". The screen shot of the error message is attached to this post.
I am trying to connect to the servers 54.204.35.135 (SAP Frontend) and 54.225.249.36 (SAP Server). Both of them I am getting the same message.
After I activate the instance on CAL, I see that on Amazon Cloud these instances are automatically started. Then I go to elastic IP and hit on associate these IPs to associate them.
Please let me know if I need to do anything else.I am using a company laptop and am afraid if these IP addresses are being blocked somewhere.
Please advise how to establilsh the RDC.
Thank you.
Regards,
Pavan.

Hi Pavan,
the following comment in your initial question draw my attention:
After I activate the instance on CAL, I see that on Amazon Cloud these instances are automatically started. Then I go to elastic IP and hit on associate these IPs to associate them.
So you started the solution (that contains 2 images) in CAL and then changed some configuration settings in the EC2 web console, correct?
It is important to understand, that changes to the configuration of the instances, that are made outside of CAL will have a severe impact. Only CAL knows how to configure both instances correctly, especially when it comes to the network and communication between each other.
If you don't mind, would you be able to shutdown and terminate all running instances of this Trial solution in CAL and start from scratch without using the EC2 web console. We have throusands of users of this system and all of them get the same software - all works. I suspect the changes in the EC2 console to be a culprit here.
All these activities should be done in CAL, not in the EC2 console:
So please terminate all instances of this solution and wait until they are completely removed.
Then go to the Solution tab and click on create instance
go through the guided procedure and pay attention on the firewall / port settings in step 3
finish and wait 30 minutes until the solution is fully started
try to connect.
Please let us know the result.
Regards,
Hannes

Remote DeskTop Connection on iMac OS X (10.6.5)

I am using RDC into work. I also have a need to use my system as do others in my home. We have 3 user accounts on the iMac and when I walk away I would like to log out of my account so others can use the system. Is there a way to do this keeping the RDC connected in the background?
Thanks
Steve

If you are referring to Microsoft's Remote Desktop Connection Client for Mac, that's a different product. As such - this forum being specifically for Apple Remote Desktop, Apple's software for managing networked Macs - you might have more luck getting suggestions if you ask in Microsoft's own forums.
Good luck.

Remote Desktop Connection/RDC display is too small on my MacBook screen

I use the free download from MS, RDC version 1.0.3 on my MacBook - to connect remotely to a PC network at my job from home. When I connect remotely the RDC display is very small on my MB screen. Is there anyway to enlarge the display or am I locked into the small size?

Thanks, Garreth. When I connect remotely with RDC, I only see "RDC" and "Help" along the top of the screen. The 'Options' link is nowhere to be found; even under each of these two tabs. Is there more than one version of RDC for Mac? It would be great if I can fill my entire MB screen (given it's already 13") with the RDC connection display.

Remote Desktop Connection (RDC) No longer working - Please help!

Ok... here we go. I cannot RDC to my network at work. I originally was using a PC and was able to connect a few times using RDC before it stopped working. It would not connect either wirelessly or connected via ethernet cable no matter what I tried. I then tried a laptop from work - same problem. I then went and bought a new Macbook Pro - connected no problem 5 times in a row until it stopped worked again out of the blue.
In summary:
- same problem exists on Macs and PCs
- same problem exists when using Wifi or Ethernet cable
- problem ONLY occurs at home with my FIOS router - all the same computers can RDC using any other network
- if I connect to my neighbor's Wifi on either a Mac or PC, it's works fine
Please help!! I've been looking at my router settings but I'm over my head. Any help would be greatly appreciated.

I am going to take an educated guess as to why, it does not work. If this does not solve the issue, please post,
The solution was posted here by user "tns", from user BigDaddy on DSLReports:
Login to your router normally, then click this link, which will take you to the now-hidden IGMP Proxy config page:
192.168.1.1/index.cgi?active_page=6059
If you are the original poster (OP) and your issue is solved, please remember to click the "Solution?" button so that others can more easily find it. If anyone has been helpful to you, please show your appreciation by clicking the "Kudos" button.

Remote Desktop Connection certification issue with Win Server 2008 R2

When connecting to Windows 2008 server R2, from Windows 7, Vista and Mac OS 10.6.7 via Remote Desktop Connection, i am getting a 'Server Name on the Certificate is Incorrect' error.
if i click connect, i can still connect to the machine, due to a 3rd party managing the server, this doesn't look very professional on my part...
The server is a standalone machine and is not currently on a domain. RDC is only used for management purposes.

Hi,
This certificate error is normal, because your client do not trust the certificate which is installed on the terminal server. To avoid this issue,
you can export the certificate and import this certificate into the client side (computer account).
Thanks.

Server 2012 RTM Remote Desktop Connection Broker Role Won't Install

Hey guys,
I have been searching for and trying fixes for this for 3 days, and I've gotten no where. Thanks in advance for trying to help me out.
Here's the situation:
I have a brand new installation of the Windows Server 2012 Datacenter 64-Bit RTM from MSDN. This is my one and only server (just my personal one for home), so I'm using this single server to run all of the services that I need. After a fresh
installation, I added the AD and DNS roles and promoted the server to the PDC. Then I go to add the Remote Desktop Virtualization Services (the VM virtualization role). The installation fails, but I can't find any explanation as to why.
I've wiped out the OS and reinstalled from scratch at leat 15 times, trying various combinations, fixes, approaches, etc. including powershell, Remote Desktop Services Deployment, standard role-based deployment, etc.
Using the role-based deployment, I can get every 'Remote Desktop Services' component to install except the Remote Desktop Connection Broker. I've tried enabling RDMSUI_TRACING, but didn't get any information at all as to why it's failing. I also
cannot find RDMSDeploymentUI.txt log.
I've also tried to deploy this using Powershell using this command:
New-SessionDeployment [-ConnectionBroker] <string> [-WebAccessServer] <string> [-SessionHost] <string>
That particular item does provide some error messages, but they seem to complain about the Session Host not being able to install due to not being able to find the connection string key in the registry for the Windows Internal Database. However, I can
get the session host and every other component to install using role-based deployment, except the Connection Broker.
I've run an SFC scan, which found no issues. I've also tried applying the one update available in Microsoft Update, and tried it without applying that update (reinstalling between attempts of course).
I'm completely at a loss. Has anyone encountered this before? Any suggestions would be greatly appreciated. Is there a powershell command for just installing the Connection Broker that might provide some additional error information, or any
information at all?
I would greatly appreciate any help anyone could offer. I'm willing to try anything. Thanks for taking the time to read this.
Sincerely,
Dominick

Also Found this:
1. You try to install the Remote Desktop Connection Broker (RDCB) on a server that also has the Active Directory Domain Server (domain
controller) role installed. This configuration is not supported by Microsoft. You need to install the RDCB on a server that does not have this role installed. See: Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012 http://support.microsoft.com/kb/2799605
2. If you don’t have the Active Directory Domain Service install, this issue might be caused by the Windows internal database (WID) that
the connection broker installs and the Windows Update KB2821895. If you have KB2821895 installed, unfortunately you can not uninstall this KB. Try to install the Remote Desktop Connection Broker (RDBC) role on a server that does not have this Windows update.
Note: There is currently no official communication from Microsoft that here is an issue with RDBC and KB2821895. However, try the RDBC installation
without this KB and see what happens.
For more information, Refer below link...
http://fabrikam.wordpress.com/2013/07/15/connection-broker-installation-failedremote-desktop-deployment-issues/

Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
or what's the problem,
Mahmoud Sabry IT System Engineer

this issue maybe will be fix by latest version, we still waiting for it
maybe your issue can be fix using this methods
https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
http://shawn.meunier.com/?p=1#comment-43

I have a time capsule connected directly to fiber connection. I have connected a windows server directly to TC and configured it for remote desktop connection. From my interanet I can access srvr but not from my home. What config I need on TC?

I have a time capsule directly connected to fibre optic point out. All pcs and macs are connected wirelessly to the internet. I have connected a windows server pc to TC. When configured for Remote desktop connection, I can access windows server from within interanet but don't know how to access it from internet. I guess I need to change some settings in TC to get some ip adress for the remote desktop connection from my home. Anyone who can help me out? Appreciate it.
Narmin

I am a little lost now.. I have read again your title and your first post.. and they seem inconsistent.
In the title you state.
From my interanet I can access srvr but not from my home.
Interanet is not a word I know.. I assumed intranet...are you talking about internet or intranet? And just to be clear say WAN or LAN.. !! Is your home part of the interanet??
In the first post you state,
I can access windows server from within interanet but don't know how to access it from internet.
Now this is more normal.. the issue is not in the home at all, it is accessible from there but fails from internet. If this is correct, then you can do a few obvious things to determine where the problem is.
But first I need to know are you actually testing from a different internet connection to your home lan.. you are not just trying the public IP from inside the LAN as that will fail due to the TC not doing NAT Loopback.
I am also assuming the TC is the only router in the network, and has the public IP on the WAN interface.
And I am also assuming you have turned on the ping responder and you can actually ping your public ip from the internet and get a response. This helps no end in figuring out where there are issues. Strange but I have no idea if there is a ping responder in the TC WAN so you might need to forward that as well. Also if you have a dynamic public ip address are you using dyndns or no-ip or some other service to connect.
1. Test bypassing the TC.. plug the internet connection straight into the windows server,, and test if you have access. If yes, the TC is the problem.. if not, your setup on the windows server is wrong.. look at firewall in particular.
2. Assuming from test 1 the TC is the problem, Post the screen shots of the port forwarding setup for us to look at.. that is by far the easiest way to check it out.
There are lots of references to port forwarding in the TC.. eg
http://must-know-mac.blogspot.com/2008/07/how-to-port-forward-time-capsule.html
The things that generally go wrong are firewall on the computer that is accepting the port.
The ISP doesn't allow connections on a particular port. (not likely in your case)
The router is behind another router.. double NAT will kill any port forward.
Upnp has already allocated a port.. not an issue as TC doesn't use upnp although a reboot of everything after you set port forwards is well worth it.. amazing how things don't stick properly without a reboot.
IP on the receiving device is not static and so changes.
Not enough or right type of ports are opened. This is always messier than it looks as one port is often not enough for two way communications.

Remote desktop connection not working in windows 7 Pro x64 bit sp1 3389 port not working

i have still facing same problem in last two week in my system RDC not working . i have installed in my system windows 7 x64 bit Pro sp1 then i check 3389 port working or not in my system use the command netstat -a -o command in
command prompt but this is my bad luck its not woking in my machine after i have decide to change RDC listening port via registry i have change it 3389 to 3391 after restart my system, and
after again testing using same command but no any change again rdc not listening . After i have search this issue on search engine google bing and microsoft , i have found more solutions but i have try one
uninstalled two microsoft updates first is kb KB2621440 second is KB2667402 and after again restart my system and again installed KB 2667402 But not change i have already enabled Remote Desktop connection in windows 7 and select the option
any version computer running , i have try three and four time enable disable remote desktop connection in my machine . but not change i have all windows firewall disable and uninstalled anti virus they intalled in my machine , and using the Mcafee
stinger tools to scan my machine to remove virus but stinger is not found any thread in system. ihave already run this command in my system sfc /scannow Please Can you help me to fix this issue.

Hi,
When you try to start the Remote Destop Connection, what errors it showed out?
Could the other PCs connect this PC with the RDC?
So you have read this blog?
RDP connections might fail due to a problem with KB2621440 - MS12-020
Did you reinstalled the KB2621440?
Besides, did you follow this guide to enable the RDC connection?
Connect to another computer using Remote Desktop Connection
And also this guide?
Why can’t I connect using Remote Desktop Connection?
Please take a check with those settings again.
Best regards
Michael Shao
TechNet Community Support

Remote Desktop Connection freezes Windows 7 64-bit

At home, I just upgraded from a Windows 7 Ultimate 32-bit desktop to a new Dell with Windows 7 Ultimate 64-bit OS. Remote Desktop Connection from my old home PC to my work PC worked great for years even after upgrading both to Windows 7 Ultimate. Now everytime I try to use Remote Desktop Connection (RDC) to connect into my work PC (with Windows Ultimate 7 32-bit) the RDC window will freeze after a new seconds of use. If I wait approx 3 minutes the RDC window will unfreeze for a few seconds before freezing again. If I minimize the RDC window on my home PC, I can continue to work because it's only the RDC window that is frozen. Here is everything I've tried already that has not helped:
1. Trying reducing the home PC screen resolution
2. Downloaded the latest 64-bit driver from NVIDIA for the GTX 260 graphics card
3. Taken my home PC to work to test behind the company's firewall--doesn't help
4. Disabled Window Auto Tuning (suggestion from this website)
5. Called Dell support--they tried for about an hour to help but couldn't; thier suggestion was to order Windows 7 32-bit version OS and install it
6. Tried running the 32-bit version of mstsc.exe - no help
7. Using MSCOMFIG, disabled all Startup items - no help
I have another home PC running Windows XP, it works perfectly using RDC to connect to my work PC. Also, I have no problem at all using RDC from my work PC back into my home PC (the other direction).
Here may be a clue: if I start up my new Dell Windows 64-bit OS in Safe Mode, the RDC session does not freeze.
Any suggestions would be appreciated!

Hi,
Since it works in Safe Mode, I suspect this should be related to some conflicts, please try the methods in the following Knowledge Base article to have a check:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
In addition, please also ensure the NIC drivers on all of the computers are up-to-date.
Hope this helps. Thanks.
Nicholas Li - MSFT

Remote Desktop Connection for Mac to Windows - logout error

Hello
I'm trying to use Remote Desktop Connection (RDC) to get from my Mac into a MacMini running Windows XP Professional. I can log into the Windows computer, but once I put in my password and click OK, it logs out of the Windows machine. Is there some sort of sharing preference or configuration that I'm missing that's making this happen?
I want to be able to use RDC to access the Windows machine and keep everything up still on the Windows machine.
Thanks

Since RDC is not an Apple product, you'll probably want to use a forum dedicated to Microsoft's Mac products such as <http://www.microsoft.com/mac/community/community.aspx?pid=newsgroups> rather than an Apple forum
Be sure to search the forum first in case someone has already had a similar question answered.

How to move Remote Desktop License's from one 2003 server to 2003/2008

Hi Sir,
We have one windows 2003 server with 5 Remote Desktop connection.
Someone hack our server and all the files (including system files) had been corrupted.
Kindly guide us the procedure to move it another server 2003/2008.
So, Please tell me the procedure recover/repair corrupted files.
The virus is something like encrypted the file and given some email to decrypt.

For migration of licenses read
http://technet.microsoft.com/en-us/library/dd851844.aspx
http://technet.microsoft.com/en-us/library/hh553155(v=ws.10).aspx
https://blogs.technet.com/b/anthoben/archive/2010/05/13/migrating-your-terminal-server-license-server-from-windows-server-2003-to-2008.aspx
http://yuridejager.wordpress.com/2011/11/10/migrating-terminal-server-licenses-from-windows-server-2003-to-windows-server-2008-r2-using-the-rd-license-manager/
http://public.madeinengland.co.nz/how-to-transfer-terminal-services-licenses-in-windows-2003-2008-2012/Hope
this helps you in migration
Milos

UAG SP4 and Windows 8.1 Remote Desktop Connection 8.1

Hello,
I found on the description of SP4 for UAG the following: "Remote Desktop: Forefront UAG SP4 supports the Remote Desktop Connection (RDC) 8.1 client." Does that apply to the publication of servers using "TS Client Tunneling
(Windows Vista/Windows XP)"?
When I use my Windows 8.1 32bit client to connect to the portal, I can see the published application, click on the icon that is on the portal and it start the SSL Application Tunneling and the SSL icon appears at the Taskbar. Then it opens the "Remote
Desktop Connection" client. However when I type the name or IP of the machine to what I want to connect, it fails. Is something wrong? Or this is not working on Windows 8.1? My windows 7 cliesnt have no problem to connect using this application.
Thank you!

Hi Rob,
Let's confirm some situation:
Did you mean connect to Windows 7 from Windows 8.1 computer?
Did you mean the printer connect to another Windows 8 computer at home, and shared to that Windows 8.1 or the printer connect to that Windows 8.1 directly?
Firstly double check your settings:
1. Launch Remote Desktop Connection.
2. Click Options, and then click the Local Resources
tab.
3. Under Local devices and resources, select the Printers check box.
After that make sure that the proper printer driver version is installed on the remote computer.
Meanwhile, refer to this thread to check the port:
http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/win-7-remote-desktop-and-local-printing-not/544acb1b-a259-4170-bc05-2c6dbfd0ca05
Karen Hu
TechNet Community Support

Remote Desktop Connection on PowerBook, not x86 iMac

My office uses SBS2003 with VPN enabled.
Without VPN, on my PowerBook & the intel-iMac, I can "Remote Desktop Connection" into the server, then subsequently into a workstation through the server.
With the VPN connected, I can use RDC to connect directly to my workstation (say, unit01).
With VPN connected, the iMac can't connect directly to the workstation, yet it can still go through the server to the workstation as usual.
I'm suspecting this is an issue with Rosetta emulating Microsoft's Remote Desktop Connection and not allowing the domain name to be recognized through the VPN.
Both computers are using the exact same settings for the VPN and attempting to use RDC exactly the same.

i've been using just the netbios name, simply because it works on my powerbook. I still don't understand why it wouldn't work on this intel-mac.
I was mainly following this guide:
http://www.smallbizserver.net/Default.aspx?tabid=266&articleType=ArticleView&art icleId=84

Remote Desktop Connection (RDC) iMac to PC server with fixed IP

Similar Messages

Maybe you are looking for