Screen locked on remote computer

ГРУППА STEAM

Steam Remote Play homestream

Присоединиться

ГРУППА STEAM

Steam Remote Play homestream

147,423
УЧАСТНИКИ

1,973

В ИГРЕ

29,393

В СЕТИ

Создана

7 ноября 2013 г.

Главная Объявления Обсуждения События Участники Комментарии

Все обсуждения > General Discussion > Подробности темы

BSlickMusic 7 фев. 2014 г. в 20:04

Screen locked on remote computer

Anyone having this issue? I played a little bit last night with no issues, but now I can't play anything at all. When I try to open anything, I get the "Screen locked on remote computer" error, and my host computer has gone to the login screen. Even after logging in to the host computer, and trying to stream again, it goes back to the login screen giving me the same error. The host computer is Win 8.1, streaming to Win 7.

< >

Сообщения 31–45 из 55

Sprinx 8 сен. 2014 г. в 13:49

Are you running it as administrator? This is required for ti to work. Maybe you should try the more thorough version posted by Heywink above.

#31

BLOOD FART 8 сен. 2014 г. в 19:17

Yeah, I made sure "run as administrator was turned on". I even copy-pasted the shortcut across from my old windows install to make sure. No dice.

I'll try HeyWink's version. I'm guessing you just paste that into the Target field?

#32

Sprinx 9 сен. 2014 г. в 7:37

I think you have to make a text file in notepad, and change the extension to .bat or .cmd for that to work.

#33

Sprinx 11 сен. 2014 г. в 16:46

Hey BattleCat, are you having the computer log in automatically once it boots up? Windows must be logged in with your user. Then you connect with RDP with the same user. Then once you run the shortcut, it throws the session back to your original login.

#34

slim 21 окт. 2014 г. в 16:42

What worked for me was that all I did was open Steam, go into my library, click my game (garry's mod in this case), and then saw it said "stream" instead of 'play". SO then I clicked the down arrow and it said play on this computer, so I clicked it, then clicked play, and boom

#35

pyro_guy7 22 окт. 2014 г. в 19:38

Which means it's installed playing off of the computer you're on, and not streaming from the other computer. That doesn't fix the problem for people that are trying to stream.

#36

spwolf 1 ноя. 2014 г. в 11:18

Автор сообщения: Sprinx
If you're using a headless PC as the game server, then every time you log into this PC via remote desktop, the screen is locked. It doesn't matter if you have a physical screen hooked to it or not.

I have my PC set to automatically log into Windows with my password (run --> "control userpasswords2". Uncheck "Users must enter a username and password to use this computer." Then enter your user and password that should be logged in each time.

This would set your PC to always be available after reboots, and you wouldn't have to log in with the keyboard.

But my main point is that after you log in with RDP, the screen is locked. If you "Disconnect" the session, then the screen remains locked until someone logs in physically at the remote computer.

To fix this, go to your desktop, right click, and choose "create shortcut"

Paste this command into the "target" field:
C:\Windows\System32\tscon.exe 1 /dest:console

Set the shortcut to always use administrative privileges. Always use this shortcut to end an RDP session - never use "Disconnect"!

This pushes your session back to the console screen (meaning the screen is no longer locked).

I use this on my HTPC all the time.

both of your solutions solved the problem for me... too bad they did not implement authentication properly, because it could be a problem for some people that you have to open up computer basically.

In any case, both of these work 100%.

#37

bat 3 янв. 2015 г. в 22:39

Tried creating the shortcut on both the server and gaming pc (you weren't specific as to which to create it on so I wasn't sure). On my gaming PC (the one I'm trying to stream to) I get the error:
"Could not connect sessionID 1 to sessionname console, error code 7045"
"Error [7045]:The requested session access is denied."

On my server it says "SessionID not found".

#38

Sprinx 4 янв. 2015 г. в 5:58

You have to go to the host (the computer that will actually be running the game) to set up the shortcut.

As Heywink suggested in post #25, one can use the Windows %sessionname% variable with this. Therefore I adjusted my own computers to do this, and I also updated my original post.

Create a new shortcut on the desktop. The command should be:

C:\Windows\System32\tscon.exe %sessionname% /dest:console

Click on the "Advanced" button on the bottom right of this shortcut. Make sure the checkbox "Run as Administrator" is selected. You can change the icon if you want, too.

#39

wzrd 4 янв. 2015 г. в 14:48

Автор сообщения: Sprinx
If you're using a headless PC as the game server, then every time you log into this PC via remote desktop, the screen is locked. It doesn't matter if you have a physical screen hooked to it or not.

I have my PC set to automatically log into Windows with my password (run --> "control userpasswords2". Uncheck "Users must enter a username and password to use this computer." Then enter your user and password that should be logged in each time.

This would set your PC to always be available after reboots, and you wouldn't have to log in with the keyboard.

But my main point is that after you log in with RDP, the screen is locked. If you "Disconnect" the session, then the screen remains locked until someone logs in physically at the remote computer.

To fix this, go to your desktop on the gaming PC (host), right click, and choose "create shortcut"

Paste this command into the "target" field:

C:\Windows\System32\tscon.exe %sessionname% /dest:console

Set the shortcut to always use administrative privileges. Always use this shortcut to end an RDP session - never use "Disconnect"!

This pushes your session back to the console screen (meaning the screen is no longer locked).

I use this on my HTPC all the time.

(Edited on 2014-1-4 to use %sessionname% variable)

This worked great. Quoting in full so others can see the solution and that Sprinx is the original poster of awesomeness.

#40

Sprinx 4 янв. 2015 г. в 17:44

Thanks for summarizing it all in one place! Hopefully this is helpful to others.

#41

bat 5 янв. 2015 г. в 20:55

Thanks that clears it up. I must have missed his post about the variable change.

#42

BadBone2k 24 янв. 2015 г. в 10:15

Автор сообщения: meneerdematthias
POSSIBLE FIX: Apparently in my case, this was a problem with SoftXpand and the new Steam Beta having RDP detection, simly adding the Steam exe's (just added all of em) to the "Tasks with RDP hiding" in SoftXpand solved it for my case. I realise this is pretty specific though but if you have anything running related to RDP (maybe teamviewer or something?) closing that and relogging into a "proper desktop session" might do the trick for you. More info also at: http://steamcommunity.com/groups/homestream/discussions/1/540732888853346946/

Thank you for this hint! With this I used information from the Miniframe Knowledge Base and added "Steam.exe *32" to the registry. Since then inhome streaming works without the constant need to switch users, to avoid the "Screen locked"-message.

http://www.miniframe.com/knowledge-base.html?catid=5&view=kb&kbartid=149

I will also contact Miniframe Support and tell them to update their “Game Definitions”, so that this step will be obsolete for future SoftXpand users.

#43

KroKoFox 26 янв. 2015 г. в 5:41

--- edit

"to late :) not seen the coment above"

--- edit

Hi,

i dont know if anyone find a solution :)

Here is mine :

Connect an RDP session. Make a CMD file with the following script :
%windir%\System32\tscon.exe RDP-Tcp#0 /dest:console
start the script and ....

its working. The desktop on the host will not lock the desktop...

Working :)

Hope this helps

Отредактировано KroKoFox; 26 янв. 2015 г. в 5:43

#44