Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Filetransfer over SMB from OSX -> Error -8062

Featured Replies

Hi everyone,
i have a problem transfering a folder to my unraid share. I allwys get an Error -8062.
Here are some Details:
Unraid 7.2 (Tiger)
Share Name: production
MacOS Compatibilioty: yes
Secured: Privat


MacOS Tahoe 26.1

I connect to my share with Apple+K
smb://192.168.1.xxx/production

I can see all my files and i can download it from that share.
I tried to upload smaler fiels up to 300mb. That worked, too

Everythinmg looks normal.

But if i grab that 49 GB Folder with a lot of files in different sizes, and drag it over it creats that folder but then i get the Error Messege


Der Vorgang konnte nicht abgeschlossen werden, da ein unbekannter Fehler aufgetreten ist (Fehler -8062).


_______

What i already tried:

- reboot of course

- tried it on a publich share. Same error

- checked: Enhanced macOS interoperability: Yes

- Tools -> New Permissions -> That Share: Still get the Error

- checked if my user has Read/Write. Yes is has.

- erased any data in Apple Keychain with anything like „._smb._tcp.local“ and did a clean connection.

- Checked the log:

log stream --predicate 'subsystem == "com.apple.smb.client"' --info

[2025/11/13 19:57:19.136678,  0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict)

  parse_dfs_path_strict: Hostname Tiger._smb._tcp.local is not ours.

[2025/11/13 19:57:19.176952,  0] ../../source3/smbd/msdfs.c:107(parse_dfs_path_strict)

  parse_dfs_path_strict: can't parse hostname from path \Tiger._smb._tcp.local

[2025/11/13 19:57:36.041858,  0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict)

  parse_dfs_path_strict: Hostname Tiger._smb._tcp.local is not ours.

[2025/11/13 19:57:36.083482,  0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict)

  parse_dfs_path_strict: Hostname Tiger._smb._tcp.local is not ours.

[2025/11/13 19:57:36.118773,  0] ../../source3/smbd/msdfs.c:107(parse_dfs_path_strict)

  parse_dfs_path_strict: can't parse hostname from path \Tiger._smb._tcp.local


Tha lead to the idea DFS isn´t working well with MacOS so i put

[global]

host msdfs = no

msdfs root = no

to the SMB Extras


Still i get this error. Any Ideas

  • Community Expert
48 minutes ago, charley said:

[2025/11/13 19:57:36.118773,  0] ../../source3/smbd/msdfs.c:107(parse_dfs_path_strict)

  parse_dfs_path_strict: can't parse hostname from path \Tiger._smb._tcp.local

These should be informational only, and unrelated to the issue, or does the time code coincide with a transfer error?

  • Author
On 11/14/2025 at 12:03 PM, JorgeB said:

These should be informational only, and unrelated to the issue, or does the time code coincide with a transfer error?

no i don´t think so. it only informational then

  • Community Expert

If there's anything else logged when the transfers fail, it may be an external issue. See if you can repeat the transfer from another PC, using a different cable/switch port.

  • Author

ok i could shrink it down.

i zipped the folder and it worked. The zip file was about 18GB.
So the Problem must have something to do with los of smaller files, subfolders and so on.

I still get the error if i thy to copy the unzipped foilder.

  • 2 months later...

I am now having the same issue as you. Also MacOS (Tahoe 26.2) and Unraid.
I can also perform the transfer if I first zip the folder, but get the error -8062 error if I don't.

Did you find a solution to this?

Thanks.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.