NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

nbhatt_14's avatar
nbhatt_14
Aspirant
Apr 21, 2016
Solved

ReadyNas 202 - Withdrawing mDNS address records / Withdrawing LLMNR address records etc...

Hi,

 

I've noticed recently my ReadyNas 202 has been "playing up". 

 

Normally I'd expect the activity light to blink away if its carrying out a back up or in use. However just recently, I've seen the activity light continually flashing at quite a rapid rate. The device is accessible via both the web interface as well as the shares through my laptop. 

 

I looked in the basic log and couldn't find anything, but I had installed the loganalyzer app and noticed the following entries continually appearing each second:

 

Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abd on eth1.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for fdbd:33c0:f95c:0:a263:91ff:fe65:4abd on eth1.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for fdbd:33c0:f95c:0:a263:91ff:fe65:4abd on eth1.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for 192.168.0.3 on eth1.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for 192.168.0.3 on eth1.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abc on eth0.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abc on eth0.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for fdbd:33c0:f95c:0:a263:91ff:fe65:4abc on eth0.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for fdbd:33c0:f95c:0:a263:91ff:fe65:4abc on eth0.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing mDNS address records for 192.168.0.2 on eth0.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Withdrawing LLMNR address records for 192.168.0.2 on eth0.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Host name conflict, retrying with Batman-278
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abd on eth1.*.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abd on eth1.*.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for fdbd:33c0:f95c:0:a263:91ff:fe65:4abd on eth1.*.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for fdbd:33c0:f95c:0:a263:91ff:fe65:4abd on eth1.*.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for 192.168.0.3 on eth1.IPv4.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for 192.168.0.3 on eth1.IPv4.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abc on eth0.*.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for 2a02:c7d:5bcc:2e00:a263:91ff:fe65:4abc on eth0.*.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for fdbd:33c0:f95c:0:a263:91ff:fe65:4abc on eth0.*.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for fdbd:33c0:f95c:0:a263:91ff:fe65:4abc on eth0.*.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new mDNS address record for 192.168.0.2 on eth0.IPv4.
Apr 21 23:42:26 Batman avahi-daemon[1615]: Registering new LLMNR address record for 192.168.0.2 on eth0.IPv4.

 

I noticed it stated there is a conflict but I have no other devices with the same name on the network. Its only recently I've started to get these messages. I've reset the box as well as router hoping it may clear any cached entries in their memory but no luck.

 

Can anyone shed any light on this.

 

System is running: Firmware:6.4.2

Feature Request & Feedback
LLMNR
mdns
  • StephenB's avatar
    StephenB
    Apr 22, 2016

    If you have both cables connected w/o any bond configured, then it makes sense that you will see a duplicate host name.  The system is likely detecting its own broadcast advertisement on the other NIC.

     

    I suggest disconnecting one of the cables, just to see if the problem disappears.  If it does, then you can reconnect the cable, and set up a suitable bond (LACP with a managed switch or an R8500, ALB or TLB with an unmanaged switch).

6 Replies

  • BrianL2's avatar
    BrianL2
    NETGEAR Employee Retired
    Apr 22, 2016

    Hi nbhatt_14,

     

    Did you factory restored your ReadyNAS? Could you get us the logs so we can have a further look?

     

    Looking forward to your response.

     

     

    Kind regards,

     

    BrianL
    NETGEAR Community Team

      • nbhatt_14's avatar
        nbhatt_14
        Aspirant
        Apr 22, 2016

        Hi StephenB,

         

        I do have both ethernet ports connected. I've had it set up like this from day one, but never encountered any issues.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More