July 1, 20251 yr How do I copy a file from KDE NEON desktop to a share on my Unraid system - I can see the share under NETWORK in KDE NEON but will not allow me to drop a file into the Unraid share folder without giving me a error - I am just starting to come over from Windows where this just happens.
July 2, 20251 yr Author Access denied.Could not write to smb://192.168.0.200/3D PRINTER DOWNLOADS/Text.txtSo the firewall is off and as I try to add a file in the share this is what I get.I can copy a file out onto my desktop but not add a file in the share.
July 2, 20251 yr Community Expert 1 hour ago, mpfcoleman said:Could not write to smb://192.168.0.200/3D PRINTER DOWNLOADS/Text.txtNormally, Linux does not like 'spaces' in file path names as a 'space' normally indicates the beginning of another parameter being passed to the shell. Normally this would be handled like this: 3D\ PRINTER\ DOWNLOADS The '\' indicates to the shell that the next character is to ignored by the shell. This may not be your problem if the shell is never involved the process but it something to keep in mind...One more thing, capitalization is another issue. Windows File system generally ignores it and Linux files system enforces it. SMB/Samba tries to handle this issue but it is not always successful. Best general advice to always match the case that is on the Linux side. (NOTE-- If there are two Linux 'sides', you had best resolve this issue by making them Identical.)
July 15, 2025Jul 15 Author On 7/2/2025 at 9:09 PM, Frank1940 said:Normally, Linux does not like 'spaces' in file path names as a 'space' normally indicates the beginning of another parameter being passed to the shell. Normally this would be handled like this:3D\ PRINTER\ DOWNLOADSThe '\' indicates to the shell that the next character is to ignored by the shell. This may not be your problem if the shell is never involved the process but it something to keep in mind...One more thing, capitalization is another issue. Windows File system generally ignores it and Linux files system enforces it. SMB/Samba tries to handle this issue but it is not always successful. Best general advice to always match the case that is on the Linux side. (NOTE-- If there are two Linux 'sides', you had best resolve this issue by making them Identical.)I done everything above but for some reason when I selected another shared folder to connect to it then prompted me for my login details and from that point I was able to connect to all shares.
July 15, 2025Jul 15 Community Expert 12 minutes ago, mpfcoleman said:I done everything above but for some reason when I selected another shared folder to connect to it then prompted me for my login details and from that point I was able to connect to all shares.Windows now requires that you actually log into an server before it will allow you to access it. (No more 'guest' logins allowed-- i.e;, 'Public' shares!) See this post and the next one on the way to automatically log into your server from Windows. https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561582
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.