Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

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 odpoveď
  • 1 má tento problém
  • 2 zobrazenia
  • Posledná odpoveď od 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.

Všetky odpovede (1)

more options

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

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