Remote desktop connection lost due to intel?

Since some time i cannot get my intel-macbook connected to my work's windows network through remote desktop connection (version 1.0.3), while i still can do so with my g5-imac. So the network does not seem to be the problem.
It used to work but now it doesn't anymore. Tried reinstalling the program, reinstalling mac os, used bin and hqx, downloaded with safari, firefox and internetexplorer, but it dos not help. Appel support directed me to this forum an window's support wouldn't talk unless i paid 300 euro's (for support on a free dowloadeable program!!).
On window's mactopia site it says "Stability is also improved (...) when Remote Desktop Connection Client is used on Macintosh computers with PowerPC G5 processors." But is the opposite true: does it not work on intel?
Who can help me out?

First, RDC does work for many folks on Intel Macs. It does have problems with printing but for the most part it's stable.
What exactly doesn't "work"? What do you see when you try to connect?
You should troubleshoot by creating a new Mac OS X user account and trying to use RDC within that account to connect to your Windows machine. If that works then you have some corrupt preferences and those are relatively easy to locate.
If you're still unable to connect then you have something at the system level that's hindering your connection. Turn off your firewall for starters. Try logging in with the Shift key held down so that you don't have any extraneous applications blocking your connection.
Finally, if your G5 works and your Intel Mac doesn't then you might want to move one machine to the other machine's network connection and verify you have the same connectivity. And verify all of this by using the same user name and password from both Macs.
Hope this helps! bill
1 GHz Powerbook G4 Mac OS X (10.4.9)

Similar Messages

Remote Desktop Connection for Mac - connection lost after a minute idle

Hi There,
I am trying to connect from a Macbook Pro to my work (XP) machine using the latest Remote Desktop Connection for Mac.
It used to work fine, and recently it has been dropping the connection if I've not been 'active' for a minute or so.
What is confusing is that it is not always like this. Some days, I can leave it inactive for hours over lunch etc, and I'll come back and it will be fine. And just the other day, in the morning it dropped me out ever minute or so I was inactive, and then the afternoon was fine, and the evening was troublsome again.
Our administrators had not changed anything during that time, nor had I changed anything on my XP machine at work, or my Mac at home.
I connect via a wireless connection.
These problems occur when running on battery and when plugged in.
Any thoughts?
Thanks,
ThreeIsles

Since RDC is not an Apple product, you should post your question on Microsoft's own forums for their Mac version of RDC:
http://www.officeformac.com/ProductForums/RemoteDesktopConnectionClient/

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.

Universal or alternativ Remote Desktop Connection client

Hi everyone,
I was wondering whether one of you, know of a better and maybe even in Universal of the Microsoft 'Desktop Remote Connection' client.
It's because I have an Intel iMac, and remotes my company desktop, but the DRC application are a bit slow in screenupdates and key strokes compared to the Windows client. I am guessing that it as to do with the Rostatta layer, which slows the application.
Any surgestion?

Hi,
I wasn’t able to find group policy setting to optimize memory usage for Windows Server 2012/2012 R2, could be due to its added new features need to consume more memory.
Besides, memory usage of remote desktop connection depends on the programs running within the session, you may try to check programs those are open within different sessions to determine which one is causing too much memory.
If memory usage is abnormally high, please keep systems fully patched.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

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

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 keeps disconnecting

I have BT Hub 3 (recently upgraded to Broadband Unlimited at the end of Jan 2015).
Up until recently I was able to Remote Desktop into my work computer (via VPN tunnel) with no problems at all.
Around March 6th, I began to experience problems with the Remote Desktop Connect (RDP), in that it now makes an initial connection and then disconnects (typically within a few seconds, occasionally after a couple of minutes).
It will then cycle through a number of reconnection attempts, all with the same result, before it finally drops altogether with the message:
'The Remote Desktop Services Session has ended. Connection to the remote computer was lost, possibly to network connectivity problems'.
I have tried restoring both machines back to a date when i know the connection was working - no joy. I've also tried deleting an re-creating now VPN and RDP connections - no joy. I've researched online and tried various other things, but still have the same problem.
I've tried connecting using a laptop (via my wirelss connection) with the same result. My manager has RDP'd in from his home machines and has had no problem at all.
This leads me to consider whether the problem is with the router/BT Hub itself. I've tried the online diagnostic tools with no resolution to this problem.
Has anyone else experienced the same problem?

Oh well, I suppose that after more than 2 months of frustration with this issue, the BTCare Community is unable to help me.
I can be fairly sure that it's not my machine as it's also happened using a laptop, plus I've even reset my PC right back to its original factory state just to sure that nothing had become corrupted.
The network guys where I work have also looked at this and can find nothing at that end to cause this problem.
I've even borrowed another BT Hub and tried it through that - same problem.
So where does the answer lie? VPN issue? I've tried other VPN options - same problem. RDP problem? I've practically exhausted the list of suggested solutions that can be found by trawling the internet.
I even upgraded the broadband cable to replace the cheap old thing that has been working perfectly well in terms of broadband, again, to eliminate this as a possibility. Now I'm stumped.
To me, it looks like the problem lies between my router and the workplace network, i.e. a physical problem among the miles of lines connecting the two. Of course I don't want to shell out for a BT engineer to come out to investigate, so I thought that the combined wisdom of this community may have been able to help.
Sadly not.

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 Solution, VPC NOT an option

I downloaded Remote Desktop Connection yesterday B/C I wanted to be able to do work on my mac, I have virtual PC with WINXP but it was way to slooow.
I do not want to play games, I play games on my compaq laptop that's in a full sized docking station.
So I was looking and reading at this software (RDC) and it sounded like a viable option, My laptop has a 14" monitor but the iMac is a 17".
so I downloaded it and set it up, BTW my connection is iMac to Laptop docking station I used a "Crossover Cable".
Set the IP address and I have (Sorry to say) windows on my MAC for nuthing!
It works great ALOT faster than VPC (since it does not have to emulate a Intel CPU).
And the Laptop monitor goes to sleep after 1 minute so now I can have the best of both worlds!

I'm not quite sure why you posted this.
You marked your post as a question... but I can't find one.
Do you have a question or was this somewhat of an "informational" post?

VPN and Remote Desktop Connection

I have a standalone windows 2012 server that runs a domain with a few workstations. I have successfully configured a PPTP VPN and can connect using a Windows 7 computer at home. Once connected to the VPN, I can Remote Desktop to the server - but not any
other computers. The computer I'm trying to connect to runs Windows 7 and has remote desktop connections enabled.
Under the Access Details in the Remote Access Management the VPN connection is shown correctly first to the router (x.x.x.1) then the server (x.x.x.2) under Protocol 17 and Port 53. Then the server is shown again under Protocol 17 and Port 3389, which must
be the Remote Desktop connection. And then the workstation on the domain (x.x.x.20) also shows a connection with Protocol 17 and Port 3389. However, the remote desktop connection fails everytime. I'm not sure where the issue exists since it appears the server
is seeing and acknowledging the remote desktop connection. On my router I have PPTP passthrough enabled and port forward 3389 to the server.
I have attempted to use the workstations internal IP address as well as the computer name (workstation and workstation.domain.local) when connecting.
Thanks for your help.
I just noticed these three event errors on the destination remote machine. Not sure why it's trying to use L2TP?
Failed to apply IP Security on port VPN2-1 because of error: A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.. No calls
will be accepted to this port.
A certificate could not be found. Connections that use the L2TP protocol over IPsec require the installation of a machine certificate, also known as a computer certificate. No L2TP calls will be accepted.
The Secure Socket Tunneling Protocol service either could not read the SHA256 certificate hash from the registry or the data is invalid. To be valid, the SHA256 certificate hash must be of type REG_BINARY and 32 bytes in length. SSTP might not be able to
retrieve the value from the registry due to some other system failure. The detailed error message is provided below. SSTP connections will not be accepted on this server. Correct the problem and try again.

Morning Trent,
I don't know if this is still an issue for you, did you get it solved?
If not, check on the server whether the user credentials that you're using to RDP to the workstation are actually authorised server-side. If that checks out, on the VPN connection you can specify a protocol to use. Specify the protocol that your VPN is configured
to use on the server.

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.

Overriding function keys when using MS Remote Desktop Connection

Is there a way when connected to a RDP client using MS Remote Desktop Connection to prevent the function keys from being intercepted and handled by OSX. For example on my iMac keyboard, function keys 7 to 12 are used to control itunes and alter the system sound volumes. Is there a way to have these keys processed by the RDP client instead, so that the remote Windows OS can handle them?
While this question currently relates to an iMac, I'll soon be using a Macbook Pro in the same scenario, and will be requiring a similar solution for that machine.

Thanks for your suggestion. Setting that option only toggles what the function keys are interpreted as in OSX, but the key presses are still not processed by the OS in the RDP session. For example, pressing F9 when the RDP window is active shows all open OSX windows in Expose, rather than having the keypress processed by the active software in the RDP session
I did try posting to the forum you mentioned yesterday, but due to server issues my post failed. I'll try again today.

Remote Desktop Connection Manager can only open 6 sessions at a time on Server 2012

I am only able to open, and view thumbnails, for a maximum of 6 RDP sessions on my Server 2012 box at a time in Remote Desktop Connection Manager (RDCM). If I add more sessions I just get a variety of connection errors for the additional sessions. If I activate
a 7th session one of the existing 6 sessions goes off-line with a connection error message. Sometimes the error says 3334, sometimes the error says 0x8345000E, and sometimes it just says there is a connection error.
I have checked Group Policy on the server to ensure I don't have any settings restricting the number of RDP sessions.
In fact, I will often have 30 or 40 RDP simultaneous sessions opened, I am just not able to view them all in RDCM. I have seen reviews of RDCM with screenshots showing dozens of thumbnails so it seems to be something that's possible to do.
Are there any settings I should make on the server to allow RDCM to connect to more than 6 simultaneous RDP sessions?
Just to be clear, all these RDP sessions are running on the same server. Also, I am just using the trial license for Server 2012 and Remote Desktop Services right now. I don't think that should have an impact, but I wanted to be thorough.

Thanks Jakub for "corflags" info.
Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll [mstscax.dll]?
Error message when making RDP connection:
Could not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
I was able to create new AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll assemblies from 64bit dll version and now it works with "AnyCPU":-)
http://www.filedropper.com/axinteropmstsclib-mremoteng
Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"
so final .dll wasn't working.
Adding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file.
Hope it helps
P.S. Sorry for possible technical misinterpretation, I am not programmer so creating new assemblies was trial-error process...

Using a remote desktop connection with the Macbook pro.

I use the remote desktop connection on the Macbook pro and am unable to exchange info between the mac and the remote connetion windows. For example, if I am writing an email from the remote connection and want to attach a document, photo etc. that I created on the Mac, it just doesn't work. It seems like the Mac and the desktop connection are completely seperated eventhough they are both on the screen in front of me. the systems I use for work are not Apple compatible and will not work on anything other than windows explorer and in my case the remote desk top connection. Any ideas!

Welcome to Apple Discussions
Try running in 'ClamShell' mode (MacBook Pro lid closed and using an external keyboard and mouse) with the Gateway connected and then run System Preferences/Displays, it should show then ...
My 1920x1080 monitor shows the following:

Remote Desktop Connection to Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

Remote desktop connection lost due to intel?

Similar Messages

Maybe you are looking for