New answers tagged smb
According this this link it is possible: https://www.chrisnewland.com/solved-mac-osx-samba-cifs-through-ssh-tunnel-error-the-server-localhost-is-available-on-your-computer-364 Finder identifies smb://127.0.0.1 as a local filesystem and refuses to mount port 445 even if you've set up an SSH tunnel using -L 445:localhost:445 The solution is to ...
workaround posted there for a very similar issue: http://osxdaily.com/2015/01/24/workaround-problem-connecting-to-server-mac-os-x-lan-discovery-error/
I have the same issue as you, no "Connect to server..." from Go menu, and Cmd-K also not work. But I accidently right-click on Finder icon on Dock and see "Connect to server..." option from there. It works for me!
Releasing Mac OS X Yosemite, Apple has updated the SMB protocol to version 3, as documented here. Windows XP, on his side, works almost certainly with the SMB 1 protocol, because the upgrade to version 2 has been done on Windows Vista, as mentioned here. The backward compatibility allows SMB 3 to connect to previous versions, but not viceversa. This issue ...
The problem here is that terminal is trying to write Unix style permissions to the CIFS share during the copy operation. When you perform "cp" via terminal the data will transfer but the fchmod command will fail as the "core CIFS protocol does not provide unix ownership information or mode for files and directories". A few solutions: Mount the share via ...
Sounds like your having issues with ownership and permissions. This might be due to storing user-X's file inside user-Y's directory. Now when user-Y tries to rename his directory, he is in effect trying to alter the attributes of user-X's file. Use the stat command to investigate. Use chown, chmod, chgrp, & chflags to make any changes.
Top 50 recent answers are included