Ask a question
Quick access
- Forums home
- Browse forums users
- FAQ
Search related threads
- Remove From My Forums
Asked by:
0
Sign in to vote
Hi enwoods01,
First of all, please ensure all the machines [both the server and the Windows 7 clients] are up to date. The latest KB for server 2016 should be KB4010672 and the latest KB for Windows 7 should be KB3212646.
Please try different credentials then check the symptom again.
I have tested on my side. It is available for me to remote to a Server 2016 from a Windows 7 machine. So the issue should be related to the specific environment.
Please check the Event Viewer for more information to troubleshoot this issue.
Event Viewer[Windows Logs\Applications, System, Applications and Services\Microsoft\Windows\Remote Desktop Services ].
Considering the issue is related to the Server 2016, we could try to ask for help from our Server forum at the same time.
Windows Server 2016 General
//social.technet.microsoft.com/Forums/en-US/home?forum=ws2016
Best regards
First of all, please ensure all the machines [both the server and the Windows 7 clients] are up to date. The latest KB for server 2016 should be KB4010672 and the latest KB for Windows 7 should be KB3212646.
Please try different credentials then check the symptom again.
I have tested on my side. It is available for me to remote to a Server 2016 from a Windows 7 machine. So the issue should be related to the specific environment.
Please check the Event Viewer for more information to troubleshoot this issue.
Event Viewer[Windows Logs\Applications, System, Applications and Services\Microsoft\Windows\Remote Desktop Services ].
Considering the issue is related to the Server 2016, we could try to ask for help from our Server forum at the same time.
Windows Server 2016 General
//social.technet.microsoft.com/Forums/en-US/home?forum=ws2016
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
.
- Edited by MeipoXuMicrosoft contingent staff Tuesday, March 7, 2017 6:37 AM
- Proposed as answer by MeipoXuMicrosoft contingent staff Friday, March 10, 2017 7:02 AM
Tuesday, March 7, 2017 6:37 AM
0
Sign in to vote
edwoods01
We had the same issue. It was due to the GPO on the Server 2016: Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level being set to "Send NTLMv2 response only. Refuse LM & NTLM". It was fixed by changing this to "Send NTLMv2 response only." If you don't have the latest Windows patches installed you may need a lower setting like "Send LM & NTLM - user NTLMv2 session security if negotiated."
Best,
Mark
- Edited by M a r k Thursday, March 21, 2019 7:45 PM
Thursday, March 21, 2019 7:45 PM