Re: Interop with Windows zeroconf/LLMNR

On Tuesday, 29 November 2016 15:23:11 IST Elazar Leibovich wrote: > Thanks, > > Even if it's up by default, which seems to be the case at least for some > Windows versions, I still want to know from people's experience, how common > it is to have someone shut it down In more than one office I

Re: Interop with Windows zeroconf/LLMNR

As hardening maybe. Windows users don't venture into the services area. PC technicians don't either. On Tue, Nov 29, 2016 at 3:23 PM, Elazar Leibovich wrote: > Thanks, > > Even if it's up by default, which seems to be the case at least for some > Windows versions, I still

Re: Interop with Windows zeroconf/LLMNR

Thanks, Even if it's up by default, which seems to be the case at least for some Windows versions, I still want to know from people's experience, how common it is to have someone shut it down. Is it a good practice? Are organization do that as a security hardening measure? Etc. On Tue, Nov 29,

Re: Interop with Windows zeroconf/LLMNR

Once upon a time I was a Windows sysadmin. Anyway, there was a nice site, called blackviper.com that listed windows services default state. However it's appears it's down now. Maybe tomorrow it'll be up? Shay On Tue, Nov 29, 2016 at 8:41 AM, Elazar Leibovich wrote: > Hi, > >

Interop with Windows zeroconf/LLMNR

Hi, It's really convenient that two Linux computers usuallly have mDNS installed by default. I can then do scp x moshe.local, to my friend's laptop. In order for that to work with Windows, one can enable Window's zeroconf standard, LLMNR. The easiest way is by configuring systemd-resolved to