Android phone on Home network -> PC on Network A = works.PC connected to Home Network -> PC on Network X = works.PC connected to Network A -> PC on Home Network = works.Same PC connected to any other network -> PC on Network A = works.PC connected to Home Network -> PC on Network A = doesn't work.Meanwhile, any PC connected to Network A can connect to Home network no problem, and Home Network PCs can connect to PCs on any other network (Network X).Īt this point, I don't know if it's a routing issue or what. Using the remote desktop app on my phone, even while connected to my Home Network's wifi, I'm able to connect to any computer on Network A. All computers on Network A seem to block any requests from the Home Network, but with one weird exception: it'll work if the request comes from an android phone. The very same computer, once connected to Network X (that is, any network other than the Home network) can connect with no issue. To be exact, the symptom is the computer on Network A prompts me for a pin number, I type it in, and then it just sits there perpetually loading (it never actually times out). Then, click on the Yes option to confirm the changes. Once the Control Panel Window opens, select Chrome Remote Desktop Host and click on Uninstall at the top. Type in Appwiz.cpl in the textbox and press the Enter key. There are 3 networks, let's call them Home, Network A, and Network X.Īny computer on my Home network attempting to connect to sessions on Network A do not make it. Follow the steps below to do so: First, press the Windows + R combination to open the Run dialog box. I am getting a chrome book in a couple of days so I have been fiddling with my remote desktop solutions.This is going to be a very nuanced problem, so I apologize for all the details. I tried Teamviewer (inelegant), Chrome RDP, (slow), and Chrome Remote desktop (best so far). But one deal breaker for me was that Chrome remote desktop doesn't match windows resolution to the client screen resolution. This is a big deal for me since the computer I am remoting into has large dual monitors, and the Chromebook I'm getting only has a 10 inch display. I had heard that "Curtain Mode" would fix this for me. So, I upgraded to Windows 10 Pro and Gave it a shot. The guide here didn't work for me at all. So here is my method to get this working.ġ. Restart your computer and see whether the black screen disappears. Right-click it and change the value to 0. Go to HKEYLOCALMACHINE\Software\Policies\Google\Chrome\RemoteAccessHostRequireCurtain. Like in the linked guide, edit the key KEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\RemoteAccessHostRequireCurtain to be equal to 1 If the directory is not present create it with google and chrome being blank strings and RemoteAccessHostRequireCurtain being of the D-WORD 32 type.Ģ. Pres s Windows + R, input regedit, and click Yes to open Regstiry Editor. I've installed Google Chrome Remote Desktop on both the host and client computers, and it connects with no problems when HKEYLOCALMACHINE\Software\Policies\Google\Chrome\RemoteAccessHostRequireCurtain is set to 0. Go to Control Panel > System > Remote Settings and make sure that remote connections are enabled and that the network authentication option is unchecked. So I installed CRD on a number of times over the years, but I've always ended up leaving it because I hate using virtual sessions because between autostarts and programs launching on the wrong session, I end up having to make sure I only have physical or virtual running. I've completed all of the steps to set up curtain mode described here, using the command in cmd in. (I'm not sure that this is necessary, but why tempt fate)ģ. Also following the linked guide, edit the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\SecurityLayer to be equal to 1. Now we make our first major departure from the guide. Open group policies and navigate to Computer\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host. First, enable Allow users to connect remotely by using Remote Desktop Services and disable Require user authentication for remote connections by using Network Level AuthenticationĪnd if all went well you are done! This will make it so that your screen resolution will automatically match the resolution of the client's display. It will also make the host computer go to a lock screen when it is remotely accessed, which could be a pro or a con depending on your use case. Another strange consequence is that if any sound is playing it will come through the speakers of both the host machine and client machine, even though the host machine will only be displaying the windows login screen. This was all tested using a Windows 10 Home laptop since it was all I have access to right now, but I will report back with the results on the Chrome book.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |