r/sysadmin•
Rob230

Suddenly RDP to several 2008R2 terminal servers is intermittent, anyone else?

Question

So this started last Thursday, all of a sudden about 20% of our 2008 R2 terminal servers started to act like they're not accepting connections, you try again and again and suddenly you get in, once logged in, you're fine.

This is very similar to what happened in January with KB2280960 but the machines in question weren't updated last Wednesday night or Thursday morn

Nothing is appearing in the logs at all during a failed attempt, nothing helpful client side. MacOS or Win10 or whatever, the issue is universal client-wise

The boxes only have on thing in common, VMware ESXi (but not a common version) and Fujitsu hardware, otherwise there is different HW Firewalls, different AV products.

I've scoured here, but I only really found back to when this happened in January. Anyone else seeing this issue suddeenly flare up?

Posted Nov 4, 2019, 10:16 AM UTC

1610
AdHocSysAdmin•

We've been dealing with that since last thursday. I've posted this to another thread:

"We (possibly) had the same issue: this morning 3 different clients with each their own 2008R2 TS on different locations reporting not being able to connect to the TS. AFAIK this started about 3 hours ago. I checked the servers but saw nothing amiss, checked clients, suspecting a Windows Update, but nothing there either. Even called the ISP of two clients (same ISP) to check if they made changes or something, but nothing. And then about half an hour ago, it's all working again."

and today

"In an attempt to figure out what is going on, I've narrowed it down to this issue being a combination of Windows 10 1903 (not fully sure, but we do have a few mac users, who are not affected by this) with Windows 2008R2 server.

Looking in the Security eventlog (example), I notice a massive amount of audit failures. Notable here is the originating workstation name frequently is "Remmina" (linux rdp client) or "Freerdp". In one series of logon failures, there was an originating IP, which (seemingly) is Ukraine based.
Account names used are "Administrator, "admin", "administrateur", "administrador" and similar common accounts.
My guess is, there's a wave of RDP hacking attempts going on, which overloads the TS, preventing genuine users to login.

Putting this to the test by IP-restricting RDP connections for some clients."

That worm is consistent with what we see in the security logs. So, yes, that could be an explanation.

9
Verneff•

Yeah, I've just run into this. Someone had pointed me to the Bluekeep vulnerability however some of the impacted machines are updated and kept frequently updated so I don't think that's the case.

They are on VMware ESXi as well, however different host hardware.

4
Dorest0rmDoing the needful•

Might be related to Bluekeep worm, servers were getting hammered with requests(security logs showed failed logins) I monitored firewall logs for a few moments, had a bunch of requests coming in from Amazonaws and blocked those ranges in the firewall. There's still requests coming in but way less than before and logging in went smoother.

3
linuxfarmer•

We had the same thing happen and our servers were getting pounded with failed login requests. Not sure if it's just a large botnet trying to exploit bluekeep or what but it was definitely a real problem.

2
poshftw•

Similar topic: https://old.reddit.com/r/sysadmin/comments/drg0g8/server_2008_r2_rdp_server_replies_ackrst_to_most/

Also if anyone affected can post NLA requirement, protocol and security levels for the affected machines?

2
midrangamo•

We just had this on Friday. It was a simple DDOS. We forced NLA and the issues went away. NLA had been turned on previous and showed as being on, but we had to switch it off, save, and then switch it back on before it stopped.

1
twisted636•

That's interesting; so you don't believe NLA was working correctly? I use GPO for our NLA settings so I haven't had any issues with this.

2
midrangamo•

It's happened a few times with other registry settings. The GUI reports a specific setting as being true, but when observed in the registry is actually set to false. Changing the setting syncs the two up. I've never figured out a good reason as to why this happens other than Microsoft updates breaking something somewhere.

Would probably be a good idea to set this via GPO since that would refresh the setting at startup...

2
m1kkel84•

We had the same issue Thursday and Friday. Massive amounts of logins. Hammering rep, can’t take anymore requests.

1