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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Reduce the RDP security level on the server not working anymore to not require network authentication.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BobbyAuthor 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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.