Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

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 Antwort
  • 1 hat dieses Problem
  • 2 Aufrufe
  • Letzte Antwort von Matt

jkmcmanus
jkmcmanus
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.

Alle Antworten (1)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

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

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