1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved Lost Network

Discussion in 'Networking (Hardware & Software)' started by buzzmag, 2016/09/26.

  1. 2016/09/26
    buzzmag

    buzzmag Well-Known Member Thread Starter

    Joined:
    2002/02/08
    Messages:
    206
    Likes Received:
    0
    Running W10 Pro with Anniversary Update.

    I use a WD MyCloud NAS connected via ethernet. I have three media players also connected via ethernet using powerlines. Never had a problem until today. Now none of the media players can find or connect to the network. The NAS doesn't appear in the Network page unless I type its address into the Network bar. Tried all of the fixes to get it to appear on the network page but nothing worked. The NAS firmware is current. The ethernet adapter has the current driver for the Qualcom Atheros AR8161 PCI-E Gigabit Ethernet Controller (NDIS 6.30). All powerlines appear to be working as they should. Wireless working with no problems.

    Running a diagnosis on the adapter gave me the attached. I've rebooted the router/modem a number of times but that didn't work. Question is the problem with my router, adapter or NAS?
     

    Attached Files:

    buzzmag,
    #1
  2. 2016/09/27
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    I would:
    1. disable IP6 on the computer network adapters (wifi & ethernet).
    2. set each media player and NAS with static LAN IP addresses. (ex. 192.168.1.2, 192.168.1.3, 192.168.1.4, 192.168.1.5)
    3. disable IP6 in the router if possible.
    4. set Homegroup services on the computer to Stop + Disabled.
    5. set advanced sharing on computer to NOT use Homegroup & to use passwords.
    6. power OFF media players, computer, NAS and router.
    7. power ON in this sequence: router > NAS > media players > computer.

    post results
     
    TonyT,
    #2


  3. to hide this advert.

  4. 2016/09/27
    buzzmag

    buzzmag Well-Known Member Thread Starter

    Joined:
    2002/02/08
    Messages:
    206
    Likes Received:
    0
    Amazing. Network is back. Thank you Tony. Gotta save this to a file for future reference.
     
    buzzmag,
    #3
  5. 2016/09/29
    buzzmag

    buzzmag Well-Known Member Thread Starter

    Joined:
    2002/02/08
    Messages:
    206
    Likes Received:
    0
    Tony,

    Sorry to report the fix stopped working. Back to the same problem. I confirmed all your recommended changes were as instructed. I suspect there's a router/modem problem and I have Comcast sending a new unit to replace the five year old I'm now using. I'll let you know if this fixes the problem.
     
    buzzmag,
    #4
  6. 2016/09/30
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    It shouldn't be a router-modem issue.
    Open a command window and try to ping each networked device.
    If successful, then it's a Windows 10 or Network Sharing Center configuration problem.
    command:
    Code:
    ping 192.168.1.x
     
    TonyT,
    #5
  7. 2016/09/30
    buzzmag

    buzzmag Well-Known Member Thread Starter

    Joined:
    2002/02/08
    Messages:
    206
    Likes Received:
    0

    Here are the ping results. All three devices are listed in my router's connected devices page. Your "shouldn't be a router/modem problem" comment gave me the idea to connect one of the devices directly to the router and my PC via HDMI. It found the network immediately and video played. Do you think it's a powerline problem? If it is, it's odd that there were no problems during the past few years. I have Network Sharing configured as you advised so it's Windows 10 or the powerlines.

    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>ping 10.0.0.04

    Pinging 10.0.0.4 with 32 bytes of data:
    Reply from 10.0.0.2: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.

    Ping statistics for 10.0.0.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    C:\WINDOWS\system32>ping 10.0.0.03

    Pinging 10.0.0.3 with 32 bytes of data:
    Reply from 10.0.0.2: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.

    Ping statistics for 10.0.0.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    C:\WINDOWS\system32>ping 10.0.0.9

    Pinging 10.0.0.9 with 32 bytes of data:
    Reply from 10.0.0.2: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.
    Reply from 10.0.0.1: Destination host unreachable.

    Ping statistics for 10.0.0.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
     
    Last edited: 2016/09/30
    buzzmag,
    #6
  8. 2016/09/30
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    Could be a powerline problem, such hardware doesn't last forever.
    If the NAS is connected by ethernet cable to the router can you ping it and access it?

    Something is awry because the responses should look like this if ping is successful:
    Reply from 10.0.0.9: bytes=32 time<1ms TTL=255
    Reply from 10.0.0.9: bytes=32 time<1ms TTL=255
    Reply from 10.0.0.9: bytes=32 time<1ms TTL=255
    Reply from 10.0.0.9: bytes=32 time<1ms TTL=255

    If unsuccessful it should look like this: (10.0.0.2 = YOUR COMP IP ADDRESS)
    Reply from 10.0.0.2: Destination host unreachable.
    Reply from 10.0.0.2: Destination host unreachable.
    Reply from 10.0.0.2: Destination host unreachable.
    Reply from 10.0.0.2: Destination host unreachable.

    but your ping results are:
    Reply from 10.0.0.2: Destination host unreachable. (generated by your comp)
    Reply from 10.0.0.1: Destination host unreachable. (generated by router)
    Reply from 10.0.0.1: Destination host unreachable. (generated by router)
    Reply from 10.0.0.1: Destination host unreachable. (generated by router)

    Probably because the devices ARE offline. That they show up in the router table of connected devices doesn't mean anything unless you reboot the router, and that sometimes won't display an updated list of devices. Most router firmware will not display a present time list of connected devices, they display a cached list.
     
    TonyT,
    #7
  9. 2016/10/01
    buzzmag

    buzzmag Well-Known Member Thread Starter

    Joined:
    2002/02/08
    Messages:
    206
    Likes Received:
    0
    Have to be away for the next two days. I was able to successfully ping the NAS but not the media players. Same failed unreachable result. They are on-line (powered-on).Looks more like a powerline problem.

    C:\WINDOWS\system32>ping 10.0.0.14

    Pinging 10.0.0.14 with 32 bytes of data:
    Reply from 10.0.0.14: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.14: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.14: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.14: bytes=32 time<1ms TTL=64

    Ping statistics for 10.0.0.14:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
     
    buzzmag,
    #8
  10. 2016/10/02
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    Looks like we've isolated the problem zone.
    Report back later.
     
    TonyT,
    #9
  11. 2016/10/02
    elcajongunsfan Lifetime Subscriber

    elcajongunsfan Well-Known Member

    Joined:
    2012/01/01
    Messages:
    377
    Likes Received:
    12
    arp -a from a DOS window. I don't get the disabling ipv6 cuz most websites, such as google and yahoo are pinged using ipv6. 70% of network problems tend to be hardware, layer 1 which is your cabling. I do like the idea of static addressing your nas device(s) Check your powerlines. Somebody in another thread had an issue with these powerline things
     
    elcajongunsfan,
    #10
  12. 2016/10/03
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,068
    Likes Received:
    396
    Not "most ", only about 22% of US networks are using IP6. And if a system has IP6 disabled then all pings are done using IP4. Disabling IP6 is not completely necessary, but when t-shooting, disabling it means one less thing to have to explore.
     
    TonyT,
    #11

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...