MacBook Pro can see MBW in finder but can't connect to it

quarkhead · June 17, 2010, 6:59pm

OK, here’s the background: Macbook Pro, 2.4, 10.6.4, fresh out of the box. Connecting to a wireless router that administers my home network. Wired to the router is a WD My Book World ethernet drive on which I store my iTunes library for the various computers in the house.

We recently moved, and had to change ISPs. I got the network up and running, and opened up my brand new MacBook from the box, and connected. No problem seeing and using the wifi connection.

However I can’t get to the ethernet drive. I can see it in the finder, under the “shared” section, but when I try to connect to it, I get the following message:

“The server “MyBookWorld” may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again.”

I tried the “connect to server” way and same message. I also tried connecting directly to the IP address of the drive. Same message.

I should add at this point, that I was able to see it and use it from my Windows 7 desktop, so I know it is accessible over the network.

I looked through the support site at Western Digital but couldn’t find anything helpful there. I searched around these forums but couldn’t find a problem that paralleled mine closely.

So I am asking the smart folks here for any help they might be able to offer. I have power-cycled the drive and the computer. And like I said it works with other computers around the house.

quarkhead · June 18, 2010, 5:32pm

Anyone have any ideas?

graemem · June 20, 2010, 11:23am

I have have been getting this message ever since I upgraded my imac from OSX 10.6.3-10.6.4 last week. I suspect its a 10.6.4 problem but it seems not to affect everyone.

WDJeremy · June 23, 2010, 9:01pm

Are you using the same router that you did on your earlier network? If you change ISPs, you should only have changed the modem. What happens if you connect the drive to your computer via Ethernet? Can your Mac access the drive without going through your network?

doc_b · June 24, 2010, 4:13am

I too am having the exact same problem with the same setup and hardware. I connected the ethernet directly to the computer but I was still unable to access the drive. The firmware is up to date. Any other suggestions?

quarkhead · June 28, 2010, 10:36pm

Well I’m not sure what I did - if anything - but it is working now. HOWEVER, today I woke up to a different problem. On my Windows 7 computer, which is connected to the router by ethernet, not wireless, I can see MYBOOKWORLD on my network but I suddenly can’t access it. It says “Windows cannot access \MYBOOKWORLD. Check the spelling of the name etc”. Now, I can still access it from my other computers on the wireless network, and in my router control panel I can see it there. Itried restarting the computer and restarting the drive. I tried the auto-diagnosing and it said: “The remote device or connection won’t accept the connection.”

WDJeremy · June 29, 2010, 11:29pm

doc-b: Can you access the drive from any other computer? Have you also tried factory resetting it?

quarkhead: If others computers can access the drive, the drive is indeed functioning. What I would do is to see if you can connect the drive directly to your Windows 7 computer to see if it then can access it.

Menageryl · July 2, 2010, 8:30pm

’ It SOUNDS to me like a drifting IP address… Are you still using the basic DHCP configuration the MyBook arrives in, or are you using static IPs? My own personal suggestion to ANYONE owning a WD NAS device is to use static IPs for all their WD NASes. This one tiny change to configurations eliminates SCORES of potential problems in one swoop!

’ Of course if you are already using static IPs then we need to look deeper. Come back to us with an answer and we’ll see if we can move forward on this.

’ That other suggestion just before mine is a good one too - let us know if you can see the device if connected directly to the Windows system via ethernet.

’ And lemme know about the IP setup.

jens001 · July 4, 2010, 8:23pm

Dear all.

I have the problem with mac mini to my book world 1.5tb. It seems that with the update to 10.6.4 the afp connection is not able to authorize to MBW. SBM and NFS works fine. BUt this is not what I want. AFP for TimeMachine worked fine for a long timeframe. I would ask you to help. Also with a new software update for MBW it doesnt work. Thx in advance.

Best regards, Jens.

quarkhead · July 19, 2010, 7:28pm

You’re way over my head.

When I connected the drive directly to my computer’s ethernet port I received the same message. It shows up as a network device, but I cannot access it.

I have my router set up as a DHCP server. Not sure how to change just the WD to a static IP, or if that will solve the problem. To my admittedly amateur sense, this doesn’t feel right. I can access it from the Mac without any problem, usually - the exception may be useful: it said to enable port 3689 when I first tried to connect this morning, but then a few minutes later was fine.

I was looking at my router setup. One thing, and I don’t know if it is normal or what it means, but: I have a netgear wireless-n 150. In the LAN setup there is something called RIP version. In the documentation it says it is defaulted to RIP_2. Mine was set to “off.” In the pulldown is listed RIP_1, RIP_2B, and RIP_2M.

I tried to set it to 2B, didn’t seem to make any difference. I don’t even know if it’s connected to the issue. As for the message about the port, I have no idea what that means.

Another reason I don’t *think* it is IP drifting, is that I can ALWAYS see it on my network, but from my windows machines I ALWAYS get the same permissions error message.

quarkhead · July 19, 2010, 7:47pm

Here’s the error:

\MYBOOKWORLD is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Not enough resources are available to complete this operation.

So there it is.

Windows 7 64 bit. Is there any other useful info that might help?

quarkhead · July 19, 2010, 8:23pm

A little more info:

We recently moved. In my old place, we had a DSL connection and I used a Gateway for my network admin. All the same computers, with the same OS and settings, were able to access MBW. Now I have a cable modem and comcast supplied me a Netgear n-150 router. It seems to me the only difference is the router and modem.

The whole thing is weird, because I can SEE MBW on the network, I just can’t access it.

Menageryl · July 21, 2010, 11:10am

’ Aha!!! You are but SO lucky!!! I just spent about 3 weeks wrestling with this problem myself. EVENTUALLY stumbled across the solution - well, at least it’s a working solution for me… Been running without this issue now for the last two weeks. Thankfully. Because it was beginning to drive me completely INSANE!!!

’ Hopefully, theoretically, this will solve the problem for you too - I know it’s already done so for at least one other person…

’ So. There are newer driver versions for the devices that are automatically installed by Windows and Windows Update. They are the cause of your problem. I’ve discovered that if you just disable them / it (uninstall not required) the problems dissapear. And, strictly speaking, as a NAS device, you have no real NEED for a driver in order to use the device.

’ So. Here’s the process - in case you need the guide. Er… I just recently had a Windows meltdown and had to re-install over two days this week - so the drivers in question haven’t yet installed and I can’t confirm the exacts here myself… But from memory, do the following:

’ Go to “Devices and Printers”

’ Find your device there. If you have more than one then you will need to do this for each and every one of them, or the problems will persist - believe it or not a single unmodified device will affect all negatively…

’ Right-click on the device, select “Properties”

’ Go to the “Hardware” tab.

’ There should be two devices listed there… One of them is listed as a “Disk Drive Device” or something of the sort. Select it, click “Properties”

’ You will need to elevate to Administrator priviliges. So click" Change settings." Confirm.

’ Then disable it - go to the driver tab, select the disable button, confirm any queries…

’ That should be that. Done.

’ Let me know how it goes for you, yeah - especially as I can’t EXACTLY remember the process right now…

’ Good luck.

quarkhead · July 22, 2010, 4:34am

I was excited to see this, so I opened up my devices page… but no such luck. It is not listed there. In a variation on your idea I actually added it. It went through the process of adding the driver but I still had the same error message when trying to open it. So I removed it from the devices.

So frustrating, because I FEEL like it must be something not terribly complicated. I mean, I know the drive WORKS fine, since I can see it and use it with my Mac. Just none of the Windows machines…

Although that original weirdness with the mac was the reason I started the thread, maybe that’s a clue - even though it seemed to fix itself, this is probably all related.

Menageryl · July 22, 2010, 11:13am

’ That is truly weird! I know this solved my identical problem - and like I said - something I sat troubleshooting and struggling with for WEEKS!

’ I Also know that the same process has also helped solve the same issue for at least two other people…

’ Unfortunately the reload of my system has completely reset the situation and there’s no way I can work the situation right now - at least not until my system gets to the point where it’s updated and configured similarly to what it was previously - something I have only finite control over.

’ Sorry. I’ll have to just get back to you if and when my system gets to that point!

quarkhead · July 29, 2010, 1:33am

Here’s the result of my network diagnosis:

Print

Windows Network Diagnostics

Publisher details

Issues found

The remote device or resource won't accept the connection

The device or resource (MYBOOKWORLD) is not set up to accept connections on port "The File and printer sharing (SMB)".

Detected

Contact your network administrator

Completed

Issues found

Detection details

6

The remote device or resource won't accept the connection

Detected

The device or resource (MYBOOKWORLD) is not set up to accept connections on port "The File and printer sharing (SMB)".

Contact your network administrator

Completed

The computer or device you are trying to reach is available, but it doesn’t support what you’re trying to do. This might be a configuration issue or a limitation of the device.

Detection details

Network Diagnostics Log

File Name:

1AA24C3E-2B5F-4669-813E-F059F6ADD908.Diagnose.0.etl

Other Networking Configuration and Logs

File Name:

NetworkConfiguration.cab

Computer Name: Windows Version: Architecture: Time:

Collection information

GAMER-PC

6.1

amd64

Wednesday, July 28, 2010 6:31:41 PM

Publisher details

Package Version: Publisher:

Windows Network Diagnostics

Detects problems with network connectivity.

1.0

quarkhead · July 29, 2010, 1:35am

More raw data:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Gamer-PC

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #2

Physical Address. . . . . . . . . : 00-04-4B-0A-10-54

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::a87c:4963:f3c3:15f1%13(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.1.x

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Wednesday, July 28, 2010 6:08:24 PM

Lease Expires . . . . . . . . . . : Thursday, July 29, 2010 6:08:24 PM

Default Gateway . . . . . . . . . : 192.168.1.x

DHCP Server . . . . . . . . . . . : 192.168.1.x

DHCPv6 IAID . . . . . . . . . . . : 318768203

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-09-15-B5-00-04-4B-0A-10-55

DNS Servers . . . . . . . . . . . : 192.168.1.x

NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet

Physical Address. . . . . . . . . : 00-04-4B-0A-10-xx

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::174:b3fe:d35c:754d%11(Deprecated)

Autoconfiguration IPv4 Address. . : 169.254.117.77(Deprecated)

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{DF065CC8-9487-4762-8523-013A9CEAF92A}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:24f2:237b:bc46:3d72(Preferred)

Link-local IPv6 Address . . . . . : fe80::24f2:237b:bc46:3d72%17(Preferred)

Default Gateway . . . . . . . . . : ::

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{3E7C59A3-ACBC-4CA3-AA34-49EB0D86C034}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Windows IP Configuration
   Host Name . . . . . . . . . . . . : Gamer-PC   Primary Dns Suffix . . . . . . . :    Node Type . . . . . . . . . . . . : Hybrid   IP Routing Enabled. . . . . . . . : No   WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
   Connection-specific DNS Suffix . :    Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #2   Physical Address. . . . . . . . . : 00-04-4B-0A-10-xx DHCP Enabled. . . . . . . . . . . : Yes   Autoconfiguration Enabled . . . . : Yes   Link-local IPv6 Address . . . . . : fe80::a87c:4963:f3c3:15f1%xx(Preferred)    IPv4 Address. . . . . . . . . . . : 192.168.1.x(Preferred)    Subnet Mask . . . . . . . . . . . : 255.255.255.0   Lease Obtained. . . . . . . . . . : Wednesday, July 28, 2010 6:08:24 PM   Lease Expires . . . . . . . . . . : Thursday, July 29, 2010 6:08:24 PM   Default Gateway . . . . . . . . . : 192.168.1.x   DHCP Server . . . . . . . . . . . : 192.168.1x   DHCPv6 IAID . . . . . . . . . . . : 318768203   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-09-15-B5-00-04-4B-0A-10-xx DNS Servers . . . . . . . . . . . : 192.168.xx NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
   Media State . . . . . . . . . . . : Media disconnected   Connection-specific DNS Suffix . :    Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet    Physical Address. . . . . . . . . : 00-04-4B-0A-10-55   DHCP Enabled. . . . . . . . . . . : Yes   Autoconfiguration Enabled . . . . : Yes   Link-local IPv6 Address . . . . . : fe80::174:b3fe:d35c:754d%xx(Deprecated)    Autoconfiguration IPv4 Address. . : 169.254.117.xx(Deprecated)    Subnet Mask . . . . . . . . . . . : 255.255.0.0   Default Gateway . . . . . . . . . :    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1   fec0:0:0:ffff::2%1   fec0:0:0:ffff::3%1   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{DF065CC8-9487-4762-8523-013A9CExxxx}:
   Media State . . . . . . . . . . . : Media disconnected   Connection-specific DNS Suffix . :    Description . . . . . . . . . . . : Microsoft ISATAP Adapter   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
   Connection-specific DNS Suffix . :    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : Yes   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:24f2:237b:bc46:3d72(Preferred)    Link-local IPv6 Address . . . . . : fe80::24f2:237b:bc46:3d72%17(Preferred)    Default Gateway . . . . . . . . . : ::   NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{3E7C59A3-ACBC-4CA3-AA34-49EB0D86C034}:
   Media State . . . . . . . . . . . : Media disconnected   Connection-specific DNS Suffix . :    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : Yes

quarkhead · July 29, 2010, 1:35am

And one more:

===========================================================================

Interface List

13…00 04 4b 0a 10 54 …NVIDIA nForce 10/100/1000 Mbps Ethernet #2

11…00 04 4b 0a 10 55 …NVIDIA nForce 10/100/1000 Mbps Ethernet

1…Software Loopback Interface 1

12…00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter

17…00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface

14…00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2

===========================================================================

IPv4 Route Table

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 192.168.1.x 192.168.1.x 20

127.0.0.0 255.0.0.0 On-link 127.0.0.1 306

127.0.0.1 255.255.255.255 On-link 127.0.0.1 306

127.255.255.255 255.255.255.255 On-link 127.0.0.1 306

192.168.1.x 255.255.255.0 On-link 192.168.1.x 276

192.168.1.x3 255.255.255.255 On-link 192.168.1.x 276

192.168.1.xx5 255.255.255.255 On-link 192.168.1x 276

224.0.0.0 240.0.0.0 On-link 127.0.0.1 306

224.0.0.0 240.0.0.0 On-link 192.168.1.x 276

255.255.255.255 255.255.255.255 On-link 127.0.0.1 306

255.255.255.255 255.255.255.255 On-link 192.168.1.3 276

===========================================================================

Persistent Routes:

None

IPv6 Route Table

===========================================================================

Active Routes:

If Metric Network Destination Gateway

17 58 ::/0 On-link

1 306 ::1/128 On-link

17 58 2001::/32 On-link

17 306 2001:0:4137:9e76:24f2:237b:bc46:3d72/128

On-link

13 276 fe80::/64 On-link

17 306 fe80::/64 On-link

17 306 fe80::24f2:237b:bc46:3d72/128

On-link

13 276 fe80::a87c:4963:f3c3:15f1/128

On-link

1 306 ff00::/8 On-link

17 306 ff00::/8 On-link

13 276 ff00::/8 On-link

===========================================================================

Persistent Routes:

None

===========================================================================Interface List 13…00 04 4b 0a 10 54 …NVIDIA nForce 10/100/1000 Mbps Ethernet #2 11…00 04 4b 0a 10 55 …NVIDIA nForce 10/100/1000 Mbps Ethernet   1…Software Loopback Interface 1 12…00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 17…00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 14…00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2===========================================================================
IPv4 Route Table===========================================================================Active Routes:Network Destination Netmask Gateway Interface Metric   0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.x 20   127.0.0.0 255.0.0.0 On-link 127.0.0.1 306   127.0.0.1 255.255.255.255 On-link 127.0.0.1 306  127.255.255.255 255.255.255.255 On-link 127.0.0.1 306   192.168.1.0 255.255.255.0 On-link 192.168.1.x 276   192.168.1.x 255.255.255.255 On-link 192.168.1.x 276   192.168.1.xxx 255.255.255.255 On-link 192.168.1.x 276   224.0.0.0 240.0.0.0 On-link 127.0.0.1 306   224.0.0.0 240.0.0.0 On-link 192.168.1.x 276  255.255.255.255 255.255.255.255 On-link 127.0.0.1 306  255.255.255.255 255.255.255.255 On-link 192.168.1.3 276===========================================================================Persistent Routes:  None
IPv6 Route Table===========================================================================Active Routes: If Metric Network Destination Gateway 17 58 ::/0 On-link  1 306 ::1/128 On-link 17 58 2001::/32 On-link 17 306 2001:0:4137:9e76:24f2:237b:bc46:3d72/128   On-link 13 276 fe80::/64 On-link 17 306 fe80::/64 On-link 17 306 fe80::24f2:237b:bc46:3d72/128   On-link 13 276 fe80::a87c:4963:f3c3:15f1/128   On-link  1 306 ff00::/8 On-link 17 306 ff00::/8 On-link 13 276 ff00::/8 On-link===========================================================================Persistent Routes:  None

quarkhead · August 9, 2010, 6:06pm

Does any of that help?

quarkhead · August 15, 2010, 6:47pm

Bumping this to see if anyone can help… does anyone from WD look at these forums? This is a frustrating issue!