Remote Desktop Connection - internal error

My laptop is running Windows 8.1 and since yesterday has starting giving problems when connecting to remote PCs using Remote Desktop Connection.
It asks for the password and then shows 'Configuring remote session' for about 30 seconds and then displays 'An internal error has occurred'. Another PC on the same network is able to connect to the remote PC without problem. I've tried connecting
to four other PCs with this laptop and two work and three don't.
I've tried changing various settings such as bitmap caching and clipboard sharing etc. Nothing makes a difference.
I've also used system restore to reverse recent windows updates and that hasn't helped either.
Any ideas?
What can cause 'An internal error has occurred'? Will it be writing to a log somewhere that I can look at to find further information about the error?
Thanks
Andy

I'm not sure if you meant there could be a problem with the user profile on the laptop or the one on the server I'm trying to connect to?
However, it seems to be the latter. I just created a new user account on the server and can now remote into it from my laptop. If I try the original user account again (Administrator) then I get the internal error message. Other client
PCs can still log-in to the server using the same Administrator account without problem.
Is there something I can do (either to client or server) to clear the fault with the Adminstrator account without wiping that account on the server?

Similar Messages

Remote Desktop Connection - Authentication error

Hello,
I wish to connect to my work PC from my laptop. The remote desktop connection was working fine till yesterday, but today i receive the following error when i try to connect -
"An authentication error has occurred. The Local Security Authority cannot be contacted. Remote Computer: <name>."
I have Win 7 ultimate installed on my 32 bit system, and have tried solutions proposed in the other threads. I do not require a NLA check for connection, i have always used the remote desktop with this option unchecked. Could anyone help me with this please?
Is this a error on my Laptop, or do i need to contact the network administrators for this?

Hi!
It could be as easy as you need to change your password on your domain accout.
Are both computers connected to the same domian or is your work computer connected to a domain and your laptop connected to a workgroup?
If your password has expired, this error can occur, so I would start to check that since it stoped working over night.
Best regards
Andreas Molin

Remote Desktop Connection Authentication Error from Windows 8.1 Pro to Windows 7 Pro

I keep trying to connect to my server running Windows 7 Pro from my laptop running Windows 8.1 Pro, but I get the following message after providing
my credentials:
"An authentication error has occurred (Code: 0x8007001f)"
I can't find any reference to this error code being associated with using remote desktop.

Hello,
Are you connecting to a server as part of a domain ? if so confirm you are using adequate credentials for remote desktop for example: username: domain\administrator
if not you can try connecting to the localhost using:
username: .\administrator - for example
also you can try running your remote connection in admin mode:
Win + R - bring up run then type:
mstsc /admin
hope that helps.
Cheers,
Harry

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

Remote desktop connection. An internal error has occurred.

Hello,
The error occurs from a Windows 7 Home computer to a Windows 7 Professional computer.
I connect successfully through a Sonic Wall VPN client.
I can ping the IP address of the remote computer.
I run remote desktop (using IP address of the remote computer) and get error:
"Remote desktop connection. An internal error has occurred."
It used to work flawlessly and all of a sudden quit working.
Please advise.

It was a VPN configuration issue on the Sonic Wall.
What was the VPN configuration issue on the Sonicwall?

Server 2012 RDS - Remote Desktop Connection Broker Client failed to redirect the user domain\username. Error: NULL

Seeing the error listed here.
The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
Pooled virtual desktop collection name: NULL
Error: Error code: 0xFFFFFFFF.
Broker and Hyper-V are on the same physical machine.
Any ideas on where to start troubleshooting this?
Used the happy wizard to create everything, and got no errors.
I have created a small pool collection, and given rights to domain users. Everything "looks" good.

I have the same problem.
(Making this long hand for those who come after)
I have installed SQl Management Studio Express 2012 SP1
http://www.microsoft.com/en-us/download/details.aspx?id=29062
(You only need the one file "SQLManagementStudio_x64_ENU.exe")
Ran this as Administrator
And typed in the Server Name field
\\.\pipe\MICROSOFT##WID\tsql\query
Then hit connect.
Expanded Databases (+sign)
Expanded RDCms
Expanded Tables
Right Clicked on rds.target, select Edit top 200 rows
Right Clicked and copied, then pasted this into a notepad file on the desktop (As a backup)
Right Clicked and selected Delete to delete the row with the data in it (and PoolID was set to Null in this row)
Did the same for rds.pool
Manually added Remote Desktop server into the MEMBER OF tab of
“Windows Authorization Access Group” via Active Directory Users and Computers. As this domain was Windows 2003 Native when the RDS server was first installed.
Rebooted server and same issue>
Checked SQL again and rows had come back.
Is that what you meant by "delete
the rds.target and rds.pool with pool id = NULL"?
Not a SQL guru, so any help appreciated.

Keyboard layout under Remote Desktop Connections (US-International)

Hi,
I'm using Microsoft's Remote Desktop Connection on Mavericks 10.9.3 to connect to a Windows 7 machine using the US-International Keyboard layout, but some keys don't seem to work (quote, double quote, ~, etc.) The Mavericks machine is set up as Language English / Region UK / Input Source US International - PC. The Windows 7 with Language English (UK) / Keyboard US International.
Any ideas?
Cheers,
Luiz
P.S.: A similar question has been raised for Mountain Lion a couple of years ago, but the solution provided was to use an external software that is not compatible with Mavericks

Even though it works under Lion, I never tried it under ML, Microsoft states
Note Microsoft Remote Desktop Connection Client for Mac (version 2.1.1) is not intended for use with Mac OS X v10.7 (Lion) or later.
So I dropped it and now I am using CoRD.

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.

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/

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 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...

HP LaserJet Pro MFP M127fn and Remote Desktop Connection

So, my pc operates on Win7-64bit. I use Remote Desktop Connection to log in to the company server, running on MS Server 2008. I purchased the HP MFP M127fn today after confirming that it is compatible with both OS listed above. I successfully installed it directly to the server via usb cord - to make sure the correct drivers downloaded to the server. I was able to test-print and print from an app while physically connected to the server. I then disconnected the printer from the server and successfully connected it to my local pc. I can test-print and print from an app on my desktop. When connect to the server via RDC, it recognizes the MFP M127fn as my default printer, and sends a print job to my local pc. I can see the job in the server print queue, I can see the print job in queue on my desktop....it spools, then says it prints, however no actual print job ever materializes.
If I select to print to the MFP M127fn fax from the server, it will open the fax window on my desktop, allow me to enter a phone number, and will dial out and send the fax. So, that driver is functioning properly.
So, my question is this: If the printer and fax claim to be successfully installed, why do I not get the print job that is sent via the server and appears in my local print queue? I get no error, either on the server side or the local desktop. They both truly think the job has printed.....but no paper ever comes out.
Our company has used several other HP printers over the years with this same set-up and have never had a problem until now. The last one was also an HP MFP - the CM1312. So, I am now completely stumped by this. I called HP support and was routed through 4 different areas before I was told that no one had a clue what the problem might be. I then called the Easy-Tech desk at Staples, where I bought the printer, and was told that it was most-likely a hardware issue and I should return the printer to swap it out for another one. If nothing would print at all, I would agree it's hardware. But, as I can print locally, I'm more-inclined to think it's driver-related......any suggestions?

Hi,
The M127fn uses the PCLmS printing language which is a lightweight printing language, a such is not supported for RDP printing.
As a reference you may find the following socument about Citrix, Terminal Services and RDP Printing, as you may find listed the M127 is not supported for a such:
http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=4aa0-8465enw&404m=secure-erc
That is clearly not an harware issue, however I suggest returning the printer and replacing it with a different model which better feet such a task.
The M225dn as an example uses a PCL 6 print driver and should provide a better feet for RDP printing using HP UPD.
Regards,
Shlomi
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

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 R2 Remote Desktop Connection Broker

I have installed RDS on a server named PLUTO on which Windows 2012 R2 datacenter is in. There is a domain controller (domain name: AGROSY) running on a Linux server. We have used Samba 3.6.6 to control the file sharing system.
When I attempt to install RDS in Server Manager, it states as following: could not retrieve the deployment information from RD connection broker server pluto.AGROSY.
Then, I searched a lot of solutions, e.g. and tried as following:
Enter-PSSession -ComputerName pluto --> which works;
but Enter-PSSession -ComputerName pluto.AGROSY --> which gives the error message as: Enter-PSSession : Connecting to remote server pluto.AGROSY failed with the following error message : WinRM cannot process the request. The following
error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.
If I ping the pluto.AGROSY, it works as well.
I have no idea how it can be solved, please help me out. Thanks a lot!

Hi,
Thanks for your comment. Sorry for late reply.
Initially please enable the PowerShell remoting in your case.
Enable-PSRemoting
http://technet.microsoft.com/en-us/library/hh849694.aspx
For FQDN name, please see that RDCB is properly configured and also certificate which you have used for RDS environment must be trusted with its private key and must match the FQDN name of the server. Did you seen the certificate has been properly used and
configured. You can go through following article for certificate and also for configuring RDCB role.
Configuring RDS 2012 Certificates and SSO
Configuring HA for the Remote Desktop Connection Broker in a 2012 RDS Farm
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Remote Desktop Connection Server 2012 Clients only using on DC as Logon Server.

I am using Server 2012 and have an RDC Server running on a VM. Originally I had ordered the licensed version as Essentials was provided to me which does not allow for a full domain environment, which is required for the RDC server. Anyway, I
used Eval versions to get started, not thinking or realizing that the DC would never be able to get Activated since it is an Eval. So after 4 days I have finally, loaded Server 2012 on a new VM, promoted to DC, Transferred FSMO roles...DNS is up and
replicating across both DC's. The Eval keeps shutting off and was going to demote it and remove, but whenever it is shutdown the Clients receive a "No Logon Servers are available " error. I start up the old DC and it works. I doublechecked
all of the roles have been moved, I checked the RDC gateway, everything points to the same Domain information, but when I check an account using 'CMD set' it shows the old DC as the Logon Server. Is there something I am missing in the RD Gateway or somewhere
else. Is there a way to force it to use the new DC? I have tried setting the options in remote desktop connection to use a particular TS Gateway setting and it doesnt seem to work. Can someone please help me think about this and offer a
suggestion or let me know if you need more info. I can figure nothing else out at this point.
Thanks so much in Advance.
-T

it sounds like your clients / rdc servers may still be pointing to the old DC for DNS.
Can you check you have updated DNS on the clients to talk to your new domain controller.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
The new DC is the only DNS server listed on the RDC Server and is the only DNS listed for the clients other than the gateway which have as a secondary. If I change the static on the old DC I cannot login, as soon as I put it back, I can login and it
shows that DC as the logon server.
I did a simple recursive test on both DNS servers....The new Domain Controller passes, the Old One which I am trying to remove, does not.
I will reply with any other updates as I continue to look into this and thanks for the suggestions.
So I also Pinged the domain from the RDC Server as suggested and it replies back with the old DC IP.
Not sure why.

Remote Desktop Connection - internal error

Similar Messages

Maybe you are looking for