Sudden problem with RDP on local network - Calgarypuck Forums - The Unofficial Calgary Flames Fan Community

GoinAllTheWay · 07-23-2020, 06:14 PM

Just discovered an issue I'm hoping someone may have an answer to.

I have a headless PC I use as my Plex server. I use RDP to connect from a couple other PC's in my house. Been working fine for ages but just recently, every time I try to connect, I get this error:

An authentication error has occured.
The Local Security Authority cannot be contacted.
Remote Computer: PlexPC
This could be due to an expired password
bla bla bla.

I haven't changed anything. One day it worked, the next it didn't. I think this may be due to a recent update.

Most google results show entries from years ago, nothing all that recent.

Anyone know how to fix? I've tried deleting the RDP icon and created a new one, same result.

accord1999 · 07-23-2020, 08:55 PM

On the Plex server, tried unchecking the "Allow connections only from computers running Remote Desktop with Network Level Authentication" option:

Fuzz · 07-24-2020, 07:22 AM

I'd try resetting the password.

TorqueDog · 07-24-2020, 08:59 AM

I know it's headless, but presumably you can connect a display to log in locally and reboot the thing? Check for updates, look at the Event Viewer, etc.? If all your machines are up to date, then having NLA enabled shouldn't matter.

GoinAllTheWay · 07-24-2020, 09:45 AM

I will try accords suggestion but ya, not sure that's it.

Yes, I do have a monitor mouse/keyboard plugged into it now. Completely up to date.

Ugh....I hate it when random/bizarre issues pop up like this. Just as I bought a few new blurays to rip. Which I can still do, just need have to sit on the floor like a chump.

Hemi-Cuda · 07-24-2020, 09:53 AM

You could always setup a free Teamviewer account and use that to access it remotely

GoinAllTheWay · 07-24-2020, 10:20 AM

Yep, that's not a bad idea. Hadn't thought of that.

But the problem solver in me can't give up just yet. There's a solution to this issue, I must try to find it first!

TorqueDog · 07-24-2020, 08:21 PM

Try the IP address instead of the hostname.

GoinAllTheWay · 07-27-2020, 10:39 AM

Tried that too, same result.

I'm pretty much out of ideas at this point. I could do the TV option but really rather have the RDP working properly.

zamler · 07-27-2020, 10:47 AM

You sure your virus checker/firewall isn't blocking the connection?

Fuzz · 07-27-2020, 10:57 AM

Check and make sure the date/time is set properly on the machine you are trying to connect to and from.

GoinAllTheWay · 07-27-2020, 11:03 AM

Quote:

Originally Posted by zamler

You sure your virus checker/firewall isn't blocking the connection?

Pretty sure? It's not throwing up an unsafe connection warning. That error usually looks a bit different and can be easily bypassed.

cmyden · 07-27-2020, 02:26 PM

A few ideas here:

https://appuals.com/how-to-fix-the-l...or-on-windows/

https://blog.mnewton.com/articles/so...-be-contacted/

-

GoinAllTheWay · 07-27-2020, 03:36 PM

I think I've read both those articles and to me, they seem to be diagnosing a new RDP connection ie something has been set up improperly.

It worked fine for 2+ yrs and only stopped working recently.

After attaching monitor and keyboard, I can sign into the system with the same PW I've used since day 1. I've never been prompted to change it. I guess to eliminate that possibility, I'll change the PW and see if that makes a difference.

GoinAllTheWay · 07-29-2020, 10:41 AM

Welp...changing PW didn't resolve the issue unfortunately.

Fuzz · 07-29-2020, 10:46 AM

Las thing I can think of is make a new user, make sure RDP is enabled for it, and see if it can connect.

Maybe also worth trying an sfc /scannow at an admin command prompt.

TorqueDog · 07-29-2020, 10:53 AM

Aside from SFC, you want to run DISM. I've brought my machines back from the proverbial dead thanks to DISM.

Run DISM /Online /Cleanup-Image /RestoreHealth from an elevated CMD prompt, and it'll do its thing. You can also do it from a Recovery Console by omitting the ONLINE switch and manually specifying your Windows directory instead.

GoinAllTheWay · 07-30-2020, 02:45 PM

Tried your suggestion, TorqueDog, same result sadly.

Will try what Fuzz suggested next but losing hope of finding an easy solution.

Can't imagine there is a drive error, they are server grade drives that are just over or under 2 yrs of age.

DoubleF · 07-31-2020, 12:58 AM

Did you install a mesh system recently? I discovered that a mesh handoff can confuse certain devices when my Anova suddenly wouldn't pair.

Pause nodes except the one directly to modem and try again? (Worked on my Anova after chatting with support)

GoinAllTheWay · 07-31-2020, 05:39 PM

Quote:

Originally Posted by DoubleF

Did you install a mesh system recently? I discovered that a mesh handoff can confuse certain devices when my Anova suddenly wouldn't pair.

Pause nodes except the one directly to modem and try again? (Worked on my Anova after chatting with support)

Yep! Sure did. But I'm pretty sure this situation predates that. I unplugged the mesh anyways and restarted the MS Surface that I use at times and issue persists.

Would this also affect wired computers too? It is impacting both, one wired and one on WiFi. PlexPC is wired too.