Please provide more information, i.e. list of chrome flags and experiments that are running.

I'm hesitant to spend time looking into this I spent some time looking at bug 887923 only to find it doesn't repro.

jam@ no flags are enabled in the chrome & it is working as expected in chrome beta #71.0.3578.44

I have an sent an email to jam@chromium.org, with login credentials. 

can you post the Variations section of chrome://version/, that'll list the experiments that are running.

Can you repro this on another machine as well?

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hi Jam@, provided the variations from Chrome://version and we don't have any other setup for Terminal Service to test the scenario.

Variations:
=================	
2c707b42-ca7d8d80
411b6d4e-f23d1dea
d01ab0d3-ca7d8d80
16e0dd70-3f4a17df
2b6ab552-ca7d8d80
66df3e9d-f2718d9f
788ec52f-3f4a17df
da89714-aea01d76
1d411afe-ca7d8d80
9041608a-3f4a17df
ca05d627-3f4a17df
c27fec31-c982d8da
7c1bc906-86bf56d9
9def365c-3f4a17df
d442dfb7-fba27fca
41e765a5-3f4a17df
4dc30737-b8a5ea08
735958b0-3f4a17df
a582a1b8-ad75ce17
8f4db35c-3f4a17df
495970ba-ca7d8d80
31e1328a-ca7d8d80
aa011017-a2d707c6
66c8e28a-d2306387
5e3a236d-59e286d0
edbcf7c5-2d3ce014
5485fc4d-3d47f4f4
87a01a8d-ca7d8d80
e111fcd-3f4a17df
9b4c4257-30ef049d
1b558915-f23d1dea
9874ae0-3f4a17df
c992f345-ca7d8d80
9e5c75f1-c9c9971c
2594bdf4-3e4b89c4
6fa07eb4-f2718d9f
4934552d-f23d1dea
7a5ba892-3f4a17df
95876445-ca7d8d80
d92562a9-4d2fac87
fc369826-3d47f4f4
7aa46da5-c946b150
67246da1-f23d1dea
58a025e3-36e97b2c
d4d220f9-1c10ba89
ad6d27cc-15e2aa9a
df072bba-ca7d8d80
8576baf1-3f4a17df
f3ea30a0-3f4a17df
23496387-232b3cab
2e7f6029-8e6f6cf9
51af0496-84708353
1fcbb124-8fbdaf71
4bc337ce-a1f4f53d
ddf77e2c-7e6113b4
494d8760-52325d43
3ac60855-486e2a9c
f296190c-20e0bb3
4442aae2-a90023b1
ed1d377-e1cc0f14
75f0f0a0-6bdfffe7
e2b18481-7158671e
e7e71889-4ad60575
b0ea13bc-dab9d9d
94e68624-f23d1dea
cc73f8a1-1776d9e
b4e8892d-3f4a17df
10a311eb-f23d1dea
7e91b7bd-c6da37cb
6204e469-e3d9cd05
81c6897f-e872b86f

I don't know what those "chrome beta" and "chrome Dev" links are on the desktop. they say remote app and prompt for a password, but that wasn't in the email. I ended up installing chrome dev and chrome beta on the machine by downloading them from google, and couldn't repro. I tried with and without the network service.

Also I don't understand why this bug, and the other one, involve remoting to one RDP session and then from it to another. Why not remote directly to the the second machine?

I guess this is not enterprise-specific? Fell free to return component if I'm wrong.

It kind of is. Not many consumers will be running a Terminal Services service.


As to jam's question why RDP in a win client to RDP into a server. It is because the Terminal Services service you are accessing from the "chrome beta" or "dev" links is only visible from inside the virtual intranet that you are becoming part of when you RDP in the first one. And exactly the second step of Chrome being streamed over RDP in the context of the Terminal Services server is what seems to collide with the new networking service.

@Kiran: Please send a mail with the credentials needed to be able to run the TS chrome inside the client VM as well the administrative account needed to directly connect to the server so that he can see what is going on on the server when the issue happens if attaching a debugger is needed.

@Jam: if you have trouble reproducing please let me or someone on the enterprise team know and we shall be able to help.

reassigning to Kiran to respond to the question above.

Thanks for the background; I got the credentials and will look into this.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5f4aded6a8c46612f1cc837e667d293968aec1c8

commit 5f4aded6a8c46612f1cc837e667d293968aec1c8
Author: John Abd-El-Malek <jam@chromium.org>
Date: Wed Nov 28 20:37:49 2018

Fix network service not working when running as a remote app before Windows 8.

r562058 made the network process always run in a job object to try to avoid it outliving the browser process. This was added to make the network process quit sooner if there was a lot of pending I/O, which happened with layout tests. Windows before version 8 doesn't support nested job objects though, so we need to stop this mitigation for those old versions.

Bug:  904361 
Change-Id: If75fc933052b1b7d4ef3d3e90664f777624c04d7
Reviewed-on: https://chromium-review.googlesource.com/c/1350977
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: James Forshaw <forshaw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611856}
[modify] https://crrev.com/5f4aded6a8c46612f1cc837e667d293968aec1c8/services/service_manager/sandbox/win/sandbox_win.cc

Verified this issue on chrome #72.0.3625.0 as steps mentioned in comment #0 and observed the URL's are loading as expected. Hence adding TE verified labels.