I just encountered this problem after using this drive for a long time under OS 10.6 and Win Vista. In short, when I try to connect to the drive as admin via the Finder in OS X, i get a "connection failed" error message. Same problems when I connect the drive directly to the ethernet port on my second Mac, a MacBook. When I boot the MacBook via BootCamp to Win Vista, the WD Discovery program sees the drive and lists the two drive letter maps to sharepoints on the drive. However, when I click on those sharepoints or try to do anything with them, I get error messages to the effect (I forgot to write down the exact messages) that the names cannot be found.
The IP address of the drive is 10.0.1.16
I cannot ssh into the drive, using "ssh 10.0.1.16" under OS X. I receive the error message "… port 22: Connection refused" when I try. I believe this is because I never set up ssh access before the drive became inaccessible. This is what a port scan shows:
Port Scanning host: 10.0.1.16
Open TCP Port: 80 http
Open TCP Port: 111 sunrpc
Open TCP Port: 139 netbios-ssn
Open TCP Port: 445 microsoft-ds
Open TCP Port: 548 afpovertcp
Open TCP Port: 55222
Port Scan has completed…
This is what arp -a shows:
~ $ arp -a
? (10.0.1.1) at 0:1f:f3:41:c7:98 on en0 ifscope [ethernet]
? (10.0.1.6) at 0:1f:f3:41:c7:98 on en0 ifscope [ethernet]
? (10.0.1.15) at 0:16:cb:b1:d4:64 on en0 ifscope [ethernet]
? (10.0.1.16) at 0:90:a9:80:51:ec on en0 ifscope [ethernet]
? (10.0.1.255) at (incomplete) on en0 ifscope [ethernet]
I can ping the drive successfully:
~ $ ping 10.0.1.16
PING 10.0.1.16 (10.0.1.16): 56 data bytes
64 bytes from 10.0.1.16: icmp_seq=0 ttl=64 time=0.273 ms
64 bytes from 10.0.1.16: icmp_seq=1 ttl=64 time=0.363 ms
64 bytes from 10.0.1.16: icmp_seq=2 ttl=64 time=0.488 ms
64 bytes from 10.0.1.16: icmp_seq=3 ttl=64 time=0.327 ms
64 bytes from 10.0.1.16: icmp_seq=4 ttl=64 time=0.416 ms
64 bytes from 10.0.1.16: icmp_seq=5 ttl=64 time=0.358 ms
64 bytes from 10.0.1.16: icmp_seq=6 ttl=64 time=0.325 ms
64 bytes from 10.0.1.16: icmp_seq=7 ttl=64 time=0.371 ms
64 bytes from 10.0.1.16: icmp_seq=8 ttl=64 time=0.224 ms
64 bytes from 10.0.1.16: icmp_seq=9 ttl=64 time=0.349 ms
64 bytes from 10.0.1.16: icmp_seq=10 ttl=64 time=0.404 ms
64 bytes from 10.0.1.16: icmp_seq=11 ttl=64 time=0.336 ms
64 bytes from 10.0.1.16: icmp_seq=12 ttl=64 time=0.406 ms
64 bytes from 10.0.1.16: icmp_seq=13 ttl=64 time=0.284 ms
^C
- 10.0.1.16 ping statistics -
14 packets transmitted, 14 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.224/0.352/0.488/0.064 ms
This is netstat output, up to this drive:
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 10.0.1.1 UGSc 19 0 en0
10.0.1/24 link#4 UCS 5 0 en0
10.0.1.1 0:1f:f3:41:c7:98 UHLWI 19 38 en0 1197
10.0.1.6 0:1f:f3:41:c7:98 UHLWI 0 53 en0 403
10.0.1.15 0:16:cb:b1:d4:64 UHLWI 0 199 en0 115
10.0.1.16 0:90:a9:80:51:ec UHLWI 0 1244 en0 1139
…
This is the lookup information for this drive:
Lookup has started…
; «» DiG 9.6.0-APPLE-P2 «» -x 10.0.1.16 any +multiline +nocomments +nocmd +noquestion +nostats +search
;; global options: +cmd
10.in-addr.arpa. 3600 IN SOA localhost. postmaster.localhost. (
2004052400 ; serial
3600 ; refresh (1 hour)
1800 ; retry (30 minutes)
604800 ; expire (1 week)
3600 ; minimum (1 hour)
This is what traceroute shows:
Traceroute has started…
traceroute to 10.0.1.16 (10.0.1.16), 64 hops max, 52 byte packets
1 10.0.1.16 (10.0.1.16) 0.422 ms 0.168 ms 0.146 ms
I can access the gui web page in my browser, but this is where I see the full error message "Warning: is_dir(): Stat failed for /DataVolume/_torrent_ (errno=5 - Input/output error) in /proto/SxM_webui/ctcs/ctcsconfig.inc on line 24." I cannot actually login via the gui. I have tried admin/admin, admin/123456, and admin with the drive pw that I set months ago; nothing works.
I have tried using the reset button on the back of the drive, both when the drive is running, and when I power the drive on (holding it for 40+ seconds). This makes no difference. admin/admin, admin/123456, and admin/mypw still do not work.
No response yet from WD tech support. (Based on what I have read here, I do not expect much from WD tech support, unless they have actually worked on the problem in the last year or so.) Has anyone found a solution that can be implemented under OS X (or by booting my MacBook to Win Vista) in light of my apparent inability to use ssh and my clear inability to log in using the gui web page? I would prefer not to take the drive out of the case, for warranty reasons. (Although I suppose I should figure out whether I am still within the warranty period.) I don't have Linux anywhere.