I turned it off and rebooted both machines yet it still won't connect... The weird thing is that it used to connect every so often, but after testing recently it doesn't seem to ever connect. And on the older firmware it would connect almost every time.
I dont think this has anything to do with Merlin FW, my guess is Microsoft recent updates (not necessery april update). I'm experiencing "weird" connections problems with Chrome Remote and I still run 380.70 on a AC88 router, three AC88 AP's and two AC66 AP's. Worked flawless for weeks and for almost a week ago CRD started to struggle.
This is what i've found so far: I'm experiencing CRD problems on both Win 1709 and 1803 builds and with different AV solutions (Norton internet security and MS Defender). Which tells me it's problably not the AV or the April update itself. But I know MS is making quite some changes in how windows is handling the network/shares/homegroups/etc these days, so thats my prime suspect so far.
There is also a chance that Chrome/CRD itself have gotten an update without me registrating it, but my gut feeling says MS is the cause. Because I experinced something of the same around the launch of Fall Creators update too.
But I absolutely do not believe it's Merlins FW which causes the CRD problems, in that case its problaby related to an Trend signature update which both 380.70 and all newer FW has gotten, which is out of his control.
Follow up:
Here's what made CRD work for me again (inhouse):
1. Start your Chrome browser ->wrench/menu ->Help ->About Chrome, and make sure it's updated.
2. Right click the start button and click on run ->Type services.msc in the run box and press enter ->Scroll down to the Function Discovery Resource Publication. Set it to Automatic. Then right click it and choose start.
3. Goto windows powersettings and make sure quick/fast start are disabled under what the on/off button should do. (also a setting which all of a sudden changed recently)
4. Never hurt to boot your machine or your router for that matter...
This also solves the issue which network machines no longer was visible in windows. This setting has recently changed on all my windows machines, both 1709 and 1803. For some reason I've been able to CRD in to a remote located windows 1709 machine. But not my inhouse (on the same network as me) windows machines (both 1709 and 1803) the last week or two. There has been sporadically connections inhouse during this period, but mostly unsuccessful and if any at all unstable.
I still believe the origin of this CRD problems has something to do with Microsoft changing the way they are handling the network (thrashing Homegroups and phasing out SMB1, etc), even though I first believed it was solved just by updating Chrome, but no.