Computer Locking When I Connect Remotely:

Certain Windows 10 computers seem to be "locking" when I connect remotely using DameWare MRC or VNC.
By locking I mean the equivalent of pressing WIN+L.
It doesn't kick me off or anything. It just locks the screen after 2-3 seconds.
If the remote user or myself unlocks the screen, it just locks again after 2-3 seconds.
At first I thought it was specific to the DameWare MRC software because that's what I use a majority of the time, but it's happening with UltraVNC as well.
This seems like such a strange issue and I'm having a hard time tracking down the cause.
I end needing to use RDP to connect but that blanks out the remote user's screen which is an issue when they are trying to show me an issue they are having.
Any ideas?
LVL 1
homerslmpsonAsked:
Who is Participating?

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

x
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.

McKnifeCommented:
And your Dameware and VNC versions claim to be fully compatible to the build number of win10 that you are using?
0
homerslmpsonAuthor Commented:
UltraVNC version 1.1.9.6 was the one I had.
Just installed the newest version from their site (1.2.1.7 - January 2018).
Same thing happened.
In this case, the remote computer is running Windows 10 Pro Version 1703 (OS build 15063.483) so while I realize this isn't the newest release of Windows 10, I certainly didn't expect to see an issue like this.
I'd upgrade him to the newest version but he's a remote user and the upgrade takes quite some time to complete.
0
homerslmpsonAuthor Commented:
And DameWare MRC is version 12.0.5.6002.
We purchased this version recently because we thought the old version we were using was the cause of this screen locking issue.
Of course now that we are seeing it while using VNC as well, it likely had nothing to do with the old version of DameWare...
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

McKnifeCommented:
My question was whether these manufacturers claim that it's compatible to your build.
0
homerslmpsonAuthor Commented:
It does appear so.
DameWare screenshot below and UltraVNC below that.
Win10aWin10b
1
McKnifeCommented:
Better ask their support personnel. Win10 is not equal in all builds. Your screenshot does not assure it works with all editions.
0
homerslmpsonAuthor Commented:
You don't find it at least a little strange that both programs are causing the same exact issue?
If it was only one, I'd reach out to that company's support, but this looks like it may be a Windows 10 thing (specific to a few builds) and not so much the remote software.
0
McKnifeCommented:
Maybe dameware has ultravnc technology incorporated... who knows.
I'd make sure that they say "it ought to work on OS build 15063.483" (several CU's behind, by the way), before I would question win10. of course another simple approach is  to install v1703 clean and see if those softwares connect alright - do that as well.
0
arnoldCommented:
check your client side settings to make sure it is not sending what appears to be a start+L

If the user's session locks, check your client settings to make sure your session is not configured to lock the screen.
This is a privacy option when removing in not to expose the system to a person on premises that will then have a loged in session ......
(A person in front of the system can easily terminate a remote session, disconnect network.)


The image you posted as mcknife pointed out, references the win10 functionality as certified in 2015.while there haven't been newer version of unc, there have been quarterly updates, two per year since.
0
homerslmpsonAuthor Commented:
There are a lot of options in both programs but nothing has been changed. The settings are 100% default.
It works on 90% of the computers without issue.
Reinstalling Windows isn't an option.
Upgrading Windows to the newest version is going to happen at some point and that MIGHT fix the issue.
I was kind of hoping that there would be an entry in the Event Viewer that I can look for or something.
0
McKnifeCommented:
You can quickly install a clean 1703, right? That would prove if it works or not.
0
arnoldCommented:
what is unclear to me is where the lock screen manifests. To the user in front of the computer, to the remote user or both.

reread the question, could you check under whose credentials do the server component on the client is running? i.e. it uses credentials that are no longer authorized or have restrictions.

I would investigate the application's logging capabilities enabling them if possible, restarting the service and trying...
0
homerslmpsonAuthor Commented:
@McKnife:
I cannot "quickly install 1703".
This computer is located at a remote location.

@arnold:
When I connect to a machine using Dameware MRC, it is using the domain Administrator credentials.  
VNC isn't using Windows credentials; it's using its own (I set a VNC password on that machine when I installed the software).
0
McKnifeCommented:
I mean locally, install a test version of win10 into a VM and use ultravnc.
0
arnoldCommented:
Vinc has its own password, you still have to authenticate into the system if locked.

If memory serves, determining the underlying cause I.e are there multiple user logged in, ...


Looking at the event log to see if any info there points to a possible cause.
0
homerslmpsonAuthor Commented:
I installed 1703 on a VM and the screen doesn't lock when connecting to it with either software.
The OS Build on this VM is 15063.0 as opposed to 15063.483 but I'm not sure how I can raise the build number.
0
McKnifeCommented:
https://support.microsoft.com/en-us/help/4018124/windows-10-update-history gives you access to all updates. Trying the latest in the vm is enough. If it still works there, update your real machine as well.
0

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
homerslmpsonAuthor Commented:
I went ahead and tried to manually download/install KB4025342 which is supposed to bring the OS Build to 15063.483.
For whatever reason, it brought the OS Build to 15063.786 (and I'm able to remotely connect to this PC without issue).
At this point I'm just going to close the question and assign you guys some points for assisting me.
0
homerslmpsonAuthor Commented:
Unfortunately, this problem wasn't "solved".
0
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.