GlassWire not seperating connections through Microsoft DirectAccess tunnel

I installed GlassWire to see what is taking up bandwidth on a remote laptop connected with Microsoft DirectAccess back to the office. Unfortunately, GlassWire seems to combine all application access into ‘Host Process for Windows Service’ and then shows our DirectAccess server as the server that all the traffic is bound to. Is there any way to separate the traffic out, either by application or by destination server, or is it just the nature of the beast?


I did some searching around and it appears Microsoft DirectAccess is purposely made to hide network activity like that for security reasons, so GlassWire can’t see anything unfortunately. It’s kind of like a local encrypted VPN if I understand correctly.

I appreciate the quick reply. Thanks!

1 Like