contherad Posted July 27, 2012 Report Share Posted July 27, 2012 Okay, I will describe the issue and then all the things i have done to try to resolve the issue.Remote Desktop Connects and then immediately disconnects when trying to remote into one particular computer.I believe this has to have something to do with this users account and I'll explain why.From a MacBook Pro running boot camp to a Mac Pro running boot camp with the same Domain User Account on this particular user RDP Connects to the the Mac Pro then immediately disconnects. I have tried to connect from a New Install on a new MacBook Pro with the same user and it does the same thing. I can remote into the Desktop on any different account. It is just this account that has the issue. From the laptop I can remote into any other computer or server just not this desktop.I tried removing the user account and re-adding it. But no luck.Any Ideas or help would be much appreciated.Thanks Quote Link to comment Share on other sites More sharing options...
richardroberts Posted July 28, 2012 Report Share Posted July 28, 2012 Hi, I'm having the same problem, I know that it's frustrating! I have a similar setup - one boot camp mac RDP to another boot camp mac, with the same user name on each. After reading your post, I tried creating a new user account (called 'temp') on the client machine, and was able to remote in with that. (thank you!!!) Before this, I have not been able to use RDP at all.My setup is a little different though - these are not domain user accounts, but just local user accounts with the same name on the RDP client and server. I did try manually specifying the other machine name in the user name when logging in, i.e. "servername\richard", as well as just leaving the default "richard" username and it doesn't make a difference (from my richard account on the client RDP disconnects immediately, but from the temp account I can log in with either form of username).I don't think that the following is relevant, but since we have a campus firewall that the server is inside, I have to connect either via Cisco VPN or SSH tunneling. In the case of the SSH tunnel, I specify the server as "127.0.0.1:3391" (where 3391 is tunneled to 3389 on the server). I don't think this is relevant though because when using the VPN I specify a regular remote server name with no special port.I found a post about a corrupt user profile causing a similar problem (http://social.techne...3-fba3a06a8216/), although I doubt that's the problem since it seems a big coincidence that we both have boot camp and also both have this issue.Also, if I look in the event viewer on the server, I see an error for every time I try to log in. It's under Event Viewer -> Applications and Services Logs -> Microsoft -> Windows -> TerminalServices-LocalSessionManager -> Operational. The EventID is 20, and the message is "Attempt to send disconnect message to Windows video subsystem failed. The relevant status code was 0xd0000008." Do you have messages like this?I've read numerous posts about bad video drivers causing this problem, however almost all of them were with NVIDIA drivers (and both client and server here have ATI cards). Also does not explain why a new user account can log in.I read a couple other things suggesting trying with home group enabled or disabled on both machines, though I haven't tried that yet.Please post if you have any progress! I'll post as well if I find anything new.Thanks,Richard Quote Link to comment Share on other sites More sharing options...
richardroberts Posted July 31, 2012 Report Share Posted July 31, 2012 Hello again, I found a good workaround to this problem. You can be logged into the client in your proper account, but run only the remote desktop client program as a different user, thus preventing the disconnection problem. You can still log in to the remote machine as your own user even though the client runs as a different user. Here's the example in my case:My username is 'richard', and I want to log in to the server as 'richard' as well:1. Logged into the client as 'richard', hold down the shift key and right-click on the 'Remote Desktop Connection' icon.2. Click 'Run as different user'.3. Run it as any other user - I created a user named 'temp' for this - but note that this other user account needs to have a password, the password cannot be empty.4. Log in to the remote machine as usual - if needed you can manually specify the user you want to connect as (though mine still defaulted to 'richard')One extra step to run as a different user, but it works around the problem entirely! Hope this helps!Richard Quote Link to comment Share on other sites More sharing options...
lesliewong Posted September 5, 2012 Report Share Posted September 5, 2012 I am having the same problem as contherad. Both my Macs are domain members. I tried richardroberts workaround and it did not work for me, even using local account credentials.I did a clean install of Windows 7 and then all the MS updates. RDP then worked. After installing Bootcamp, I had the immediate disconnect problem.In the event log of the Mac I'm trying to log into, I get an 4005 event ID, "the Windows logon process has unexpectedly terminated."I uninstalled bootcamp and RDP started working again. Without bootcamp, I can't control things like brightness, the dedicated function keys don't work and there is no trackpad support except for the hardware driver.Before unintalling bootcamp, I tried turning off the two Apple services, Apple OS Switch Manager and Apple Time. I was still unable to connect via RDP. I'm now trying to find if I can remove components of bootcamp and still have the other services. Quote Link to comment Share on other sites More sharing options...
richardroberts Posted September 11, 2012 Report Share Posted September 11, 2012 lesliewong, in google searching about this problem, I read about a lot of compatibility problems with the bootcamp drivers/services, even them causing several different types of RDP issues, which is congruent with what you found. One of the things that I read about more problems with were the boot camp video drivers, and the error code (in event log) on my machine had something to do with the "video subsystem". Disabling the bootcamp video drivers might be a good next thing for you to try - though I'm not sure how to disable those drivers - it's not the same method as for disabling a service.johhny-marshal, thanks but I don't think internet connection or a virus would explain it, since RDP works fine for me when run as a different user and fine for lesliewong when bootcamp is not installed? Quote Link to comment Share on other sites More sharing options...
richardroberts Posted October 2, 2012 Report Share Posted October 2, 2012 It's been nice having you guys as companions dealing with this problem :-) However, recently, maybe due to some updates, RDP has been working fine for me, even without the "different user" workaround. Have you guys had any changes for the better lately as well? Quote Link to comment Share on other sites More sharing options...
contherad Posted November 15, 2012 Author Report Share Posted November 15, 2012 I am still having the issue. Anyone find a solution? Quote Link to comment Share on other sites More sharing options...
MANEMAN Posted November 15, 2012 Report Share Posted November 15, 2012 Hi there.Which Windows operating system are you using ? Quote Link to comment Share on other sites More sharing options...
contherad Posted November 16, 2012 Author Report Share Posted November 16, 2012 Windows 7 Professional (64-bit) for both the laptop and the desktop. Quote Link to comment Share on other sites More sharing options...
MANEMAN Posted November 17, 2012 Report Share Posted November 17, 2012 Just done a very quick read through the help you have had from past posters.O.K. So you've changed over now from Mac to Windows, or are perhaps running Windows on a Mac. Four months have gone past and you still have the same problems.As richardroberts seemed to have a pretty good grip on the subject maybe you could send him a message.( http://forums.window...?showuser=23378 )As I am not now sure if we are talking about problems in a Mac or a Windows environment. I will stay out of the way of your subject. ( Windows I would presume, as you have posted on a Windows forum.)Do consider 3rd party software for remote access. ( Although over a period of 4 months of inconvenience I expect you may have already gone down that path.)Here is a list of links for "Remote Desktop Access" for both Mac and Windows : >>>>>>>>> http://www.similarsi.../teamviewer.com and also http://www.google.co...iw=1284&bih=586.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=.=The subject of remote desktop completely aside you may also be interested in - "A network file-sharing application that makes sending a file to another machine on the local network as easy as dragging and dropping.""The application can be easily configured within a few simple clicks, and doesn’t require users to configure OS-specific file sharing settings.""Nitroshare works on Windows, Mac OSX and Linux." FREE !Download it here: >>>>>>>>>> https://launchpad.net/nitroshare/Best of luck in your quest.John. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.