The RDP client is 6. Correct that I don't have the settings ticked for network level. I have checked both the remote desktop in control panel, and also the session collection properties. I have just also put it into group policy that it is disabled. It does, however seem logical that this is the issue, but I cannot find anywehere to disable it. I will try enabling it, and then disabling it again. Therefore I think I can eliminate NLA from the issue, and focus on the message regarding "The remote session was disconnected because the remote computer received an invalid licensing message from this computer".
These refer to windows , but the keys exist in slightly differnet location on Deleted and remote now works. I can connect once from a windows server, but then the keys recreate and I cannot connect subsequently until I repeat this again.
Does it work? Also, you can try these troubleshooting steps from the following article. Meanwhile, please help me collect any related log in Event Viewer on the Server Thanks for the suggestions. I have previously tried deleting the client MSLicensing reg setting, and worked through the article. A couple of event logs below.
The first one occurs at approx. The second is logged when I attempt to login. Two things I can say - first is that a windows 7pc or windows server can remote desktop to this server ok. Access to this namespace might be denied if the script or application does not have the appropriate authentication level.
I then reinstated just remote desktop session host, leaving all other elements coming from Server A. Once this was reinstated I again cannot connect from a client. If I have NLA enabled in the session collection then it will not connect, but gives an appropriate message. If I disable NLA it gives me the licencing error, so it is communicating correctly with the infrastructure.
No authentication protocol was available. However, I've checked all URLs you gave to me and I'll use the last one to turn on userenv debug logging to try to gather additional information. I also must say that I've double-checked all network-related and hardware-related aspects. The problem lies somewhere in 's compatibility with XP because all Windows 7 clients that share the same network, hardware, settings etc.
It can be antivirus, network connection, old drivers or patches missing. Also, take a look at the below article, if it applies. DC never had an antivirus and I've tried to disable and even uninstall antivirus from XP workstations.
I have even tried a fresh XP installation. This is definitely not a network issue because Windows 7 clients located in the same physical and logical network are working properly. All drivers and patches on all systems are up-to-date. I will do it now and surely post here if there will be something interesting. Thank you a lot for the links; I'll follow them now. I've also noticed a strange behavior. XP workstations cannot browse shares on DC, but they can browse shares on R2 RDS that is in the same domain with the same policies.
For more details see Microsoft KB The solution is to modifying the registry on the Windows XP client. Try it on one workstation and add it to a group policy script if it resolves your issue. Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Add a comment. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science.
Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related Hot Network Questions.
0コメント