This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Can't add attachment on iMac from external network drive, can see drive but not access even tho it works find in Word and Finder.

  • 1 پاسخ
  • 1 has this problem
  • 2 views
  • آخرین پاسخ توسّط Matt

more options

I have a new WD Cloud external drive on my home network, and am working on two iMacs. On both iMac's I cannot insert an image in a Thunderbird email or attach a file from that drive. When trying to do so, I can see the drive and it's folders, but they are all grayed out and inaccessible. I CAN insert images into Word on the iMacs from the same WD drive, and the files on it are fully accessible from Finder. Thunderbird on a Windows 7 laptop also successfully accesses files stored on the WD drive. I have "mapped" the drives on the iMacs per the WD instructions. Any clue as to how I can solve this? It's most frustrating. Thanks.

I have a new WD Cloud external drive on my home network, and am working on two iMacs. On both iMac's I cannot insert an image in a Thunderbird email or attach a file from that drive. When trying to do so, I can see the drive and it's folders, but they are all grayed out and inaccessible. I CAN insert images into Word on the iMacs from the same WD drive, and the files on it are fully accessible from Finder. Thunderbird on a Windows 7 laptop also successfully accesses files stored on the WD drive. I have "mapped" the drives on the iMacs per the WD instructions. Any clue as to how I can solve this? It's most frustrating. Thanks.

All Replies (1)

more options

perhaps the last comment on the bug linked below offers a workaround.

https://bugzilla.mozilla.org/show_bug.cgi?id=378425