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

Forum Discussion

timeroon's avatar
timeroon
Aspirant
Jun 12, 2018
Solved

D6400 attached device not connecting to LAN

Hi all. I have a D6400 that I have installed the latest firmware on. When I plug in various laptops ect they apear in the attached devices list with no problem and get assigned an IP. I have a web sensor device that has an IP of 192.168.1.213 and it does not appear in the attached devices list at all when I connect with ethernet cable. The sensor does not have wireless capability.  I know the web sensor and cable works because if I plug it into a BT homehub 3 it connects and works properly. Why does it not work with the Netgear modem router please? Any help or advice would be much appreciated. Thank you.

  • > D6400 [...]
    > The web sensor has the IP address of 192.168.1.213 set by the
    > manufacrturer by default [...]

       Ah.  Sorry.  I was thinking "R", not "D".  The D6400 has a default
    LAN IP subnet of "192.168.0.*", not "192.168.1.*".  No doubt, the other
    router used "192.168.1.*".  If you're unwilling or unable to change the
    address of "The web sensor" to match the default D6400 subnet, then
    you'd need to change the LAN subnet of the D6400: ADVANCED > Setup > LAN
    Setup : LAN TCP/IP Setup : IP Address.

       After the change, you should restart everything, and, with "The web
    sensor" and the D6400 (and its other client devices) on the same subnet,
    all should be able to communicate with each other.

5 Replies

  • > [...] I have a D6400 that I have installed the latest firmware on.

       An actual version number would be more useful than your opinion of
    what's "the latest" today.

    > [...] I have a web sensor device that has an IP of 192.168.1.213 and
    > it does not appear in the attached devices list at all when I connect
    > with ethernet cable. [...]

       How do you know its IP address (whatever it is)?  My D7000 does not
    show all active devices in its "Attached Devices" report, so such an
    absence says little about whether the gizmo is connected.  See:

          https://community.netgear.com/t5/x/x/m-p/1585918

       Have you tried a command like "ping 192.168.1.213" from some computer
    on your LAN?  Is the problem that you can't communicate with the gizmo,
    or that it fails to appear in the "Attached Devices" report?

    > [...] Why does it not work with the Netgear modem router please?

       Bad (or badly documented/understood) router firmware?

    • timeroon's avatar
      timeroon
      Aspirant

      Hi antinode and thank you for the reply.

       

      The firmware loaded is 1.0.0.78 which says it is the current version on the website however I just noticed in the top support articles there is a version 1.0.0.80 so I will try that .

       

      The web sensor has the IP address of 192.168.1.213 set by the manufacrturer by default and when I plugged it into the BT homehub 3 and put that IP into my web browser it came up with the data as it should. This is not the case with the Netgear unfortunately.

       

      Yes I pinged it on  Linux and Windows machines and through the netgear there is no connection and it is not in the attached devices report. When I ping it with the other modem router all is ok. 

       

      Thank you once again for your help.

      • antinode's avatar
        antinode
        Guru

        > D6400 [...]
        > The web sensor has the IP address of 192.168.1.213 set by the
        > manufacrturer by default [...]

           Ah.  Sorry.  I was thinking "R", not "D".  The D6400 has a default
        LAN IP subnet of "192.168.0.*", not "192.168.1.*".  No doubt, the other
        router used "192.168.1.*".  If you're unwilling or unable to change the
        address of "The web sensor" to match the default D6400 subnet, then
        you'd need to change the LAN subnet of the D6400: ADVANCED > Setup > LAN
        Setup : LAN TCP/IP Setup : IP Address.

           After the change, you should restart everything, and, with "The web
        sensor" and the D6400 (and its other client devices) on the same subnet,
        all should be able to communicate with each other.