Have you ever tried to remotely access someone else’s computer in your office, just to be shot down by a “can not connect” line? This is a quick tutorial on how to evade that little bugger, and enable remote access, remotely.
Step 1: The problem
Noticing you have the problem, would obviously have to be the first step. If you don’t have this problem, no need to fix it.
Step 2: Open up Regedit
First real step is open up registry editor (start, run, regedit), and locate “Connect Network Registry…”
Step 3: This is what will happen
Once that is opened, locate your offending PC, this is what it should look like when all is said and done.
Step 4: 1 more search
Find HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server
And locate the Key fDenyTSConnections
Step 5: Change the value
Change the value from 1 to 0, now you can connect
I’ve encountered this issue many times, and when an issue happens in a remote office, this saves you a boat load of driving time. Hope it helps at least one spicehead out there.
465 Spice ups
Thanks for posting that. Need it from time to time. I thought it required one reboot after changing the value. Is that true?
I would say it wouldn’t hurt to reboot, but I haven’t run into any issues just doing it right away.
I ran in to this exact problem the other day for one of our remote sites, perfect thanks!
gglines
(TSTSGreg)
April 10, 2013, 1:38pm
5
I have searched and searched for a way to do this remotely and so far nothing has worked. This worked flawlessly. Thanks!
awesomeee, i have been searching for this long time ago.
Thank you for sharing
nice, I hate getting home and wanting to log into someones pc to look at something but RDP was not on. Thanks for sharing!
I’ve never had to reboot to do this, but occasionally have to wait up to 30 seconds for it to take effect.
Also, if you’re on Windows 7 you may need to start the remote registry service first before you can edit the registry remotely.
michael1259
(Network Overlord)
April 10, 2013, 3:32pm
9
You can also set a group policy.You can also set a group policy.
scub
(hsc5775)
April 10, 2013, 4:06pm
10
anthony
(Twon of An)
April 10, 2013, 4:06pm
11
Like bobjam said, you’ll have to have Remote Registry service enabled:
Set-Service remoteregistry -ComputerName $Computer -status Running
anthony
(Twon of An)
April 10, 2013, 4:06pm
12
Like bobjam said, you’ll have to have Remote Registry service enabled:
Set-Service remoteregistry -ComputerName $Computer -status Running
This is awesome! Thanks so much for the write up on this!
z-rogue
(Z-Rogue)
April 10, 2013, 4:08pm
14
this is awesome, but i’m hitting an error, related to needing both computers to have remote registry enabled?
matt248
(Matt9169)
April 12, 2013, 6:02pm
15
.bat file with the below line, and run using psexec, no reboot needed.
@reg add “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server” /v fDenyTSConnections /t REG_DWORD /d 0 /f
Also wondered about this but never been bothered to look it up,
Thx for sharing ^^
sam
(skrysiak)
June 7, 2013, 8:32am
17
I’ve run into the problem of being unable to connect to remote machines a few times now, and as many of these computers are too distant to be worth travelling to it’s great to see a simple way of rectifying it from across the network. Ace write-up!
crmcathy
(CRMCathy)
August 6, 2013, 3:13am
18
This sounds awesome - thank you! Does it also work when the PC is locked?? ie - can you “wake up” the PC?
Cool very helpful, i think this time i am able to solve my problem.
Simple script i add a batch file from AD
“reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server” /v fDenyTSConnections /t REG_DWORD /d 0 /f”"
save the file anyname.bat and done.