KB4103718 broke our ability to RDP in to one of our servers

Servers: Windows Server 2008 R2 Standard SP1.
Clients: Windows 7 Pro SP1.

Last week, as soon as KB4103718 was installed on the clients, they couldn't connect to one of our servers (error is attached here). They could connect to the other one though.

I just looked on both servers and that KB is pending, wanting to install.

Why would the behavior be different on the two machines? I want to make the second one function with RDP like it always has. My only resolution so far is to go to each clinet machine and uninstall that KB, and then disable auto updates so it doesn't get installed again, but obviously that's not a real solution.
Who is Participating?
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Reduce the RDP security level on the server not working anymore to not require network authentication.
QMBBAuthor Commented:

That sure looks like the cause, because the settings on both servers were different. I'm going to reinstall that KB on a users client and test, but a question first:

Everybody who RDPs into these servers are either on our LAN which is inside our SonicWall hardware firewall, or they are VPN'ed in via Aruba hardware. Does changing this setting to NOT require network level auth compromise us security-wise?
Short answer is: lowering security levels well... lowers security. It does not compromise a system di per se
Long answer here: https://technet.microsoft.com/en-us/library/hh750380.aspx
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.