My Book Live 2TB loses connection

Hi, 

Please forgive me if there is another thread on this topic, but I cannot seem to find one that relates to my issue.

I have a MBL 2TB drive. Ever since I bought it, (Black Friday) I have had nothing but issues with the connectivity.

The drive continuously loses connection to my computers on my network.

I can successfully ping the drive through my CMD prompt. However, the drive mapping will be inaccessible and I cannot not access the dashboard through the IP address in a browser.

Only power cycling the drive will allow me to see the drive on any machine. My connection to the drive will then last between 30 min and 2 hours before the same thing happens again.

I have the drive connected directly to my router, and have a Static IP assigned to the drive. I have tried assigning a static IP both inside and outside of my DHCP range, same effect.

I have 1 Win7 pro 64Bit Desktop

1 Win7 Premium home 32bit laptop

1 Vista 64 bit desktop.

and one Macbook Pro running Mavricks

All computers show this issue

All PC’s on are on the same workgroup and can see each other through the network. 

Only The MBL is having issues. As I mentioned above though, even when I cannot access the drive through the mapped drive or the IP Address in my browser, I can still successfully ping the drive. The drive also shows up in my network list on my router.

Only after power cycling the MBL and then remapping the drive can I access my folders.

Thank you for your time.

1 Like

No real solution, but I had a close similar problem with a 2TB MBL.  My MBL was connected to a switch which was connected with a long cable to the router.  My AVR kept losing the connection & a reboot of the MBL was necessarily  done to get the AVR reconnected/recognized; no problems with the blu-ray player; both the AVR & blu-ray player are “made” by the same company…

The solution was achived by accident in that I decided to change connection of the long cable from the router to another switch next to the router.  No more problems!!??!!  Why?  I don’t know as the cable was the same cable & why didn’t the MBL see the AVR but was able to see the blu-ray player?  Decided not to investigate further & leave well enough alone; not knowledgeable enough to know why a switch box works better than the one in the router.

The strange thing is that I decided to go somewhat wireless & got rid of the long ethernet cable wrapping around the door to the next room.  Got a wifi extender & used it in bridge mode & the AVR & blu-ray player connected via cat5e; the wifi extender ethernet ports are set of connect to the router at the 5 mhz mode.  Everything still works; perhaps the 2.4 wifi is disrupting but not everything?

Just to let you know a solution is possible for strange things that sometimes happen.

I have the “EXACT” same issue

Hi all. Just registered because of this issue.

I think I’m having a similar issue:

Every 20 minutes to 1 hour (seems random) WD My TV loses connection to the MBL. I’m just playing a video (with zero issues), then all of the sudden it stops the video and a message pops up “Lost connection to media server” (or some similar message).

I’m using a Technicolor tg784nv3 router. The Wifi signal could be better, but it’s usually constant.

I will try to use another router, or connect MBL to a different port on the router, just to check if it’s an issue with MBL or the wifi connection itself.

Does anyone read these posts? :slight_smile:

I have seen the same after updating to current firmware.
Using a port scanner, I can additionally see that the http, https & smb ports are no longer listening (twonky ports were still active). I updated to the WD DLNA server in case Twonky was an issue on the later firmware, but I get the same (with the added issue that the drive seems permanently active, even with the Ethernet port disconnected (drive head movements can still be heard along with flashing indicator), so I’m less inclined to reboot now together my 30 mins use again :frowning: ).
Any thoughts WD?

More info:

Upon rebooting the MBL (& enabling ssh access so that I at least have a way to shutdown without the dashboard), I see the following active ports:

Ports- 1-21: closed

  • 22: open
    Service: ssh (SSH Remote Login Protocol)
  • 23-79: closed
  • 80: open
    Service: http (HTTP)
  • 81-110: closed
  • 111: open
    Service: sunrpc (SUN Remote Procedure Call)
  • 112-138: closed
  • 139: open
    Service: netbios-ssn (NETBIOS Session Service)
  • 140-442: closed
  • 443: open
    Service: https (HTTP over SSL/TLS)
  • 444: closed
  • 445: open
    Service: microsoft-ds (Microsoft-DS)
  • 446-547: closed
  • 548: open
    Service: afpovertcp (AFP over TCP)
  • 549-2048: closed
  • 2049: open
    Service: nfs (Network File System)
  • 2050-2868: closed
  • 2869: open
    Service: icslap (ICSLAP)
  • 2870-3688: closed
  • 3689: open
    Service: daap (Digital Audio Access Protocol (iTunes))
  • 3690-9977: closed
  • 9978: open
    Service: xybrid-rt (XYBRID RT Server)
  • 9979-10023: closed

Then after a while ( actually lasted a good few hours this time) I can only see the following:

Ports- 1-21: closed

  • 22: open
    Service: ssh (SSH Remote Login Protocol)
  • 23-547: closed
  • 548: open
    Service: afpovertcp (AFP over TCP)
  • 549-2048: closed
  • 2049: open
    Service: nfs (Network File System)
  • 2050-2868: closed
  • 2869: open
    Service: icslap (ICSLAP)
  • 2870-9977: closed
  • 9978: open
    Service: xybrid-rt (XYBRID RT Server)
  • 9979-10023: closed

At this point I have no dashboard, or access to my shares, but DLNA is still running. I didn’t realise it until I compared results, but it looks like the iTunes server is dead also.

Running processes whilst ports are down ( in case it helps):

ValeNAS1:~# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 May11 ? 00:00:00 init [2] root 2 0 0 May11 ? 00:00:00 [kthreadd] root 3 2 0 May11 ? 00:00:00 [ksoftirqd/0] root 4 2 0 May11 ? 00:00:00 [watchdog/0] root 5 2 0 May11 ? 00:00:00 [events/0] root 6 2 0 May11 ? 00:00:00 [khelper] root 9 2 0 May11 ? 00:00:00 [async/mgr] root 89 2 0 May11 ? 00:00:00 [sync_supers] root 91 2 0 May11 ? 00:00:00 [bdi-default] root 93 2 0 May11 ? 00:01:03 [kblockd/0] root 98 2 0 May11 ? 00:00:00 [ata/0] root 99 2 0 May11 ? 00:00:00 [ata_aux] root 101 2 0 May11 ? 00:00:00 [kseriod] root 121 2 0 May11 ? 00:00:00 [rpciod/0] root 152 2 0 May11 ? 00:00:00 [khungtaskd] root 153 2 0 May11 ? 00:00:47 [kswapd0] root 154 2 0 May11 ? 00:00:00 [aio/0] root 155 2 0 May11 ? 00:00:00 [nfsiod] root 156 2 0 May11 ? 00:00:00 [kslowd000] root 157 2 0 May11 ? 00:00:00 [kslowd001] root 161 2 0 May11 ? 00:00:00 [xfs_mru_cache] root 162 2 0 May11 ? 00:00:00 [xfslogd/0] root 163 2 0 May11 ? 00:00:00 [xfsdatad/0] root 164 2 0 May11 ? 00:00:00 [xfsconvertd/0] root 165 2 0 May11 ? 00:00:00 [crypto/0] root 264 2 0 May11 ? 00:00:00 [scsi_tgtd/0] root 276 2 0 May11 ? 00:00:00 [scsi_eh_0] root 279 2 0 May11 ? 00:00:00 [scsi_eh_1] root 308 2 0 May11 ? 00:00:00 [btn_t] root 316 2 0 May11 ? 00:00:00 [a3gblink_t] root 375 2 0 May11 ? 00:00:05 [md0_raid1] root 377 2 0 May11 ? 00:00:01 [kjournald] root 1648 1 0 May11 ? 00:00:00 udevd --daemon root 2089 1 0 May11 ? 00:00:01 logsave -s /var/log/fsroot 2383 1 0 May11 ? 00:00:25 /usr/sbin/rsyslogd -c3root 2628 2 0 May11 ? 00:00:39 [jbd2/sda4-8] root 2629 2 0 May11 ? 00:00:00 [ext4-dio-unwrit] root 2963 1 0 May11 ? 00:00:00 dhclient3 -pf /var/runroot 3916 1 0 May11 ? 00:00:00 /usr/sbin/ifplugd -i eroot 3967 1 0 May11 ? 00:00:00 /usr/local/bin/resetbtroot 4308 1 0 May11 ? 00:00:18 /usr/local/bin/upnp_naroot 4890 1 0 May11 ? 00:00:00 /sbin/mdadm --monitor root 4913 1 0 May11 ? 00:00:00 /usr/sbin/sshd root 4929 1 0 May11 ? 00:00:00 /bin/sh /usr/local/sbiroot 4945 1 0 May11 ? 00:00:06 /bin/bash /usr/local/sroot 4987 1 0 May11 ? 00:00:00 /sbin/rpc.statd root 5012 1 0 May11 ? 00:00:00 /usr/sbin/rpc.idmapd root 5036 2 0 May11 ? 00:00:00 [lockd] root 5037 2 0 May11 ? 00:00:00 [nfsd] root 5038 2 0 May11 ? 00:00:00 [nfsd] root 5039 2 0 May11 ? 00:00:00 [nfsd] root 5040 2 0 May11 ? 00:00:00 [nfsd] root 5041 2 0 May11 ? 00:00:00 [nfsd] root 5042 2 0 May11 ? 00:00:00 [nfsd] root 5043 2 0 May11 ? 00:00:00 [nfsd] root 5044 2 0 May11 ? 00:00:00 [nfsd] root 5055 1 0 May11 ? 00:00:00 /usr/sbin/rpc.mountd -root 5066 1 0 May11 ? 00:00:02 /usr/sbin/nmbd -D root 5139 1 0 May11 ? 00:00:00 /usr/sbin/netatalk -F root 5141 5139 0 May11 ? 00:00:05 /usr/sbin/afpd -d -F /root 5142 5139 0 May11 ? 00:00:00 /usr/sbin/cnid_metad -root 5171 1 0 May11 ? 00:00:00 /usr/local/bin/mDNSResroot 5540 1 0 May11 ? 00:03:48 /usr/local/bin/mpe_serroot 5551 1 47 May11 ? 05:23:12 /usr/local/bin/dms_smmroot 5618 1 0 May11 ? 00:00:01 /usr/sbin/cron root 5632 1 0 May11 ? 00:00:00 /usr/local/bin/lld2d eroot 5711 1 0 May11 ? 00:00:13 ./miocrawler root 5746 1 0 May11 ? 00:00:04 /usr/orion/communicatiroot 5851 1 0 May11 ttyS0 00:00:00 /sbin/getty -L ttyS0 1root 7424 1 0 04:58 ? 00:00:00 openvpn /CacheVolume/.root 16098 4929 0 07:57 ? 00:00:00 sleep 1800 root 16971 4913 0 08:12 ? 00:00:00 sshd: root@pts/0 root 16986 16971 0 08:13 pts/0 00:00:00 -bash root 17033 4945 0 08:13 ? 00:00:00 sleep 60 root 17034 16986 0 08:13 pts/0 00:00:00 ps -ef root 19612 2 0 03:14 ? 00:00:00 [flush-8:0] ValeNAS1:~#

I solved this way:

My configuration: Router Asus DsL55U …
To stay connected:

  1. set the dhcp of the router to assign ip to a certain number
  2. set the static ip of the MBL off the field dhcp router
  3. Set the doors of MBL on the router
  4. create a vpn to the router (otherwise it will only work if you are on the same network)
  5. when you need to connect with your smartphone or tablet or PC, activate the vpn and then connect via the WD Wd my cloud or photos.

P.S. if you are on the same network, of course, the vpn should not be enabled (not required)

I hope I was helpful.

1 Like

Hi Battle,
I think you’ve answered the wrong thread. This one relates to the MBL becoming inaccessible on the local network.

my problem was both locally and remotely. I did a reset of the MBL, set the router’s DHCP to assign IP starting from 192.168.1.2 to 192.168.2.200 while the MBL I set static IP of 192.168.1.210. Now it works.

Sorry if I misunderstood the question but my English and very bad. :wink:

Hi all.

Regarding my issue with Technicolor tg784nv3 router, i finally solved it!

Not the best solution, however:

I had to set up a second router, so basically my home network (wired and wireless) connects to the second router (it’s an older DLink model), and this second router connects to Technicolor. DHCP is enabled on Technicolor, and disabled on the second router.

So DLink is basically working as a switch and providing wireless.

This has finally solved my WD TV Live connection issues!!

Took me about 3 weeks to finally come to this solution…

I’m having exactly the same problem with a Technicolor TG784n v3 fouter, which is widely used by our main telecom operators in their fibre optics service. I had contacted WD technical support and in the end of a long story they said to make an RMA. I did it, and when I received the replacement disk, the same problem immediately appeared. Since this problem is affecting more customers it must be an incompatibility of the current firmware with such router.

Does WD support team monitor this threads? Are they aware of the problem? Only they could fix it in future firmware update.