Difference between revisions of "Access Microsoft Workgroup Shares with OSX"
From Free Knowledge Base- The DUCK Project: information for everyone
(Created page with "==Connect MacOSX Catalina 10.15.x to Windows Workgroup NAS cifs 1.0== Set the workgroup * Apple -> System Preferences -> Network (icon) -> Advanced (button) -> WINS (tab) * N...") |
m |
||
| Line 5: | Line 5: | ||
* NetBIOS Name: set the name your computer will appear as on the windows network | * NetBIOS Name: set the name your computer will appear as on the windows network | ||
* Workgroup: set at your windows workgroup name | * Workgroup: set at your windows workgroup name | ||
| + | |||
| + | CIFS is roughly the same as SMB version 1 (it's more complicated than that, but they're close enough for our purposes). Apple's implementations of SMB version 2 (introduced in OS X v10.9) and version 3 (OS X v10.10) were a bit buggy, at least at first. If you use an "smb://" URL in the connect dialog, it'll use the newest version that both the server and client support, and if you're still seeing weird behavior from that... then you can use "cifs://" to force it back to the old version 1 protocol, which might fix it | ||
| + | |||
| + | ==Alternative NAS Solution: Enable AFP== | ||
Revision as of 18:42, 4 July 2020
Connect MacOSX Catalina 10.15.x to Windows Workgroup NAS cifs 1.0
Set the workgroup
- Apple -> System Preferences -> Network (icon) -> Advanced (button) -> WINS (tab)
- NetBIOS Name: set the name your computer will appear as on the windows network
- Workgroup: set at your windows workgroup name
CIFS is roughly the same as SMB version 1 (it's more complicated than that, but they're close enough for our purposes). Apple's implementations of SMB version 2 (introduced in OS X v10.9) and version 3 (OS X v10.10) were a bit buggy, at least at first. If you use an "smb://" URL in the connect dialog, it'll use the newest version that both the server and client support, and if you're still seeing weird behavior from that... then you can use "cifs://" to force it back to the old version 1 protocol, which might fix it
