Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Works perfectly now! You, sir/ma'am, are legend. Thanks!
#!bin/bash
wakeonlan 00:00:00:00:00:00
This part is missing a / before bin.
I have developed a one-click-solution for the streaming logon problem. It bases on a Windows service and TCP request.
- No RDP or other remoting program needed
- No "always auto logon"
- No admin rights needed for gaming account
Features:
- Logon on remote computer by sending a TCP request (no session like RDP).
- I have only developed a Powershell script for sending the request, but it would also work on a Linux and Steam Link.
- Integrated Wake-On-Lan functionality.
- Could be setup as fully automated solution with just powering up your Steam Link.
Unfortunately, it is a bit more complex to setup but once it is done, the usage is easy.
I have made all (service, scripts) open source, so if you are interested check it out on GitHub:
https://github.com/dwettstein/Steam_AutoLogon_Service
I'm open for any improvement suggestions or pull requests on GitHub.
Cheers
I need some more explanation on the reasoning behind some choices.
For instance, why the need for an extra account on the host machine? I'd really prefer to avoid it. Is it to avoid logging in with administrative rights?
The start phrase works as an extra password to avoid sending the user password unencrypted?
What's the explanation for point #9 in the instructions? What does the Remove-Autologon script achieve?
Also, if I'm not mistaken, there's no way to lock the machine once streaming ends, right? You should add it, I think.
I like the fact that it can be setup through firewall rules to work only on local network.
This guide should have you covered.
http://wol.aquilatech.com/
Was kind of tricky to set up at first, but after using "search for machines" I found my device and can now easily turn it on and remote into it. You still need that shutdown script and after using RemoteDesktop, you have to push your session to the local console, for which you need the Pro version of windows.
You install the "server" app onto the host PC (small memory footprint that runs as background service) and then control the computer from the phone app. Wake on LAN, restart / shutdown / sleep / logoff / hibernate, screen on / off, on-screen keyboard, mouse control, Remote Desktop without locking screen, Volume control, windows media center control / itunes / spotify / xmbc / plex / vlc, etc. control, view / open files and folders on pc, transfer files between phone and pc, virtual WiFi hotspot, password protection, encrypted data transmission, domain support, etc.
Cost: $0
I use this exclusively for in-home streaming. Host PC runs Windows 10 on an Intel system (Ethernet) and client is a Windows 10 AMD system (AC WiFi). From within the app I wakeup both computers from sleep (or from powered-off state), stream whatever game that I want to play and then put both systems to sleep (or shutdown) when I'm done. Nice and easy.
I had to adjust the target using Breno's Suggestion... ALSO, the app was renamed "wakeonlan" NOT "wakeUPonlan"...
so, this is what I used in the game shortcut settings...
"Target" ...
/bin/bash -c "/usr/local/bin/wakeonlan 00:00:00:00:00:00"
"Start in"
/bin/
Be sure to use YOUR computers MAC ADDRESS. NOT "00:00:00:00:00:00"
Thanks!!!