Help please: Network Service Discovery Disabled

[Peter Silva]

oops! on systemctl it is called 'avahi-daemon.service' not just 'avahi.service'
just double checked.
sorry.


On Fri, Dec 16, 2016 at 10:54 AM, Peter Silva <peter at bsqt.homeip.net> wrote:
> Depends on version of ubuntu...
>
> if  >= 16.04  (with systemd as init system)
>
> #stop the running daemon:
> systemctl stop avahi.service
>
> # prevent start in future:
> systemctl disable avahi.service
>
>
> I don't have earlier versions handy... but they will be different because
> of upstart.
>
> #stop the running daemon
> service avahi-daemon stop
>
> # prevent start in future:
> update-rc.d avahi-daemon disable
>
> I'm just quoting from here for the earlier versions:
> http://askubuntu.com/questions/205937/how-can-i-disable-avahi-daemon
>
>
>
> On Fri, Dec 16, 2016 at 10:09 AM, Charles IRONS <irons.charles at gmail.com> wrote:
>> Hi Peter Silva
>>
>> I am happy to turn off avahi but have not found any way to do that in man
>> pages or Ubuntu How To.
>>
>> The TP-LINK user guide has masses of instructions that just confuse me. I am
>> a retired end user.
>>
>> Please give me guidance or commands.
>>
>> Thanks & kind regards.
>> --
>> Our preferred address is
>> irons.charles at gmail.com
>> Home   +2783 588 0028
>>
>> On Mon, 2016-12-12 at 08:39 -0500, Peter Silva wrote:
>>
>> Does anyone know of a practical useful service that is discovered by
>> avahi? I know it is supposed to provide discovery, but it's never
>> discovered anything on my networks, so I always just turn it off,
>> especially because it tends to be unhappy about something most of the
>> time.   I have the vague recollection of it breaking DNS also.
>>
>> On Mon, Dec 12, 2016 at 6:29 AM, Nils Kassube <kassube at gmx.net> wrote:
>>
>> Charles Irons wrote:
>>
>> I keep getting this warning. My new TP-LINK router still connects as
>> Auto Ethernet but maybe I should change some configuration if you can
>> send me terminal commands.
>> "Network Service Discovery Disabled" appears on my screen with the
>> message below that I could not copy.
>> So I scanned Syslog and found the details below. Upper case is my
>> edit. I have a text file with more of syslog if you want that.
>>
>> Dec  4 16:15:53  Charles-PC avahi: AVAHI DETECTED THAT YOUR CURRENTLY
>> CONFIGURED LOCAL DNS SERVER SERVES
>> A DOMAIN .LOCAL. THIS IS INHERENTLY INCOMPATIBLE WITH AVAHI AND THUS
>> AVAHI DISABLED ITSELF. IF YOU WANT TO USE AVAHI IN THIS NETWORK,
>> PLEASE CONTACT YOUR ADMINISTRATOR AND CONVINCE HIM TO USE A DIFFERENT
>> DNS DOMAIN, SINCE .LOCAL SHOULD BE USED EXCLUSIVELY FOR ZEROCONF
>> TECHNOLOGY.
>>
>>
>> There are no terminal commands - the message says it all: the fault is
>> at the configuration of the TP-Link router because it uses the .local
>> domain which is reserved for zeroconf. If you want to use zeroconf /
>> avahi services, have a look at the router configuration. Maybe there is
>> a way to change the local domain name to something different. But
>> beware, there is no domain name reserved for local use (AFAIK), so you
>> should check that the name you select isn't in use already on the public
>> internet.
>>
>>
>> Nils
>>
>>
>> --
>> ubuntu-users mailing list
>> ubuntu-users at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>
>>
>>
>> --
>> ubuntu-users mailing list
>> ubuntu-users at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>