Mar 16, 2018 Step 2 – Connect to Windows Shared Folder from OS X. Finally, on the Mac, open Finder and look under the Shared section for the Windows 10 PC. If Shared is not in the sidebar, you have to add it. With Finder open, click on Finder and then Preferences at the top. Click on Sidebar and check all the items under Shared. Jan 29, 2015 I just upgraded to Windows 8 from Windows 7 (I have a whole new computer) and now I can't connect to my Mac's shared drive. I can see the drive in Network, and I can put in my User Name and Password, but it keeps telling me that the User Name or Password is incorrect. I know it is correct. Aug 19, 2016 Hi, We have 2 Mac Late 2013 MacPro machines that were both running Yosemite OS. 1 of the Mac randomly unmounts Windows 2008 R2 SMB shares while the other one doesn't (they are both using the same shares and the same software accessing those same shares). Mar 24, 2020 When you store files in iCloud Drive, you can share them with Mac computers, iOS devices, and Windows PCs. Learn about iCloud Drive. External storage device. With an external storage device, such as a hard drive or USB flash drive, you can transfer even large amounts of data from one computer to another. Other computers on the same network. Mar 16, 2018 Access Mac HFS+ Partitions From Windows. RELATED: How to Install Windows on a Mac With Boot Camp Apple’s Boot Camp driver package automatically installs an HFS+ driver for Windows, which allows Windows to see your Mac partition. This partition shows up as “Macintosh HD” under Computer on your Windows system. There’s a big limitation here, though — the driver is read-only.
Apple's Time Machine is the go-to backup method for many Mac users. Apple's termination of the AirPort series puts some users in a lurch over how they will be continuing to back up their Macs using Time Machine when Time Capsule is no more. Luckily there a few Apple approved Time Machine backup optionssans Time Capsule.
However, not everyone will be able or willing to use a spare Mac as a backup location or attach yet another external drive or even buy an expensive Time Machine capable NAS. There do exist other hacked solutions that will allow you to use any networked location — including a Windows share. Although this method cobbles together various utilities to make it function (and as such could be subject to points of failure), you can easily set up Time Machine to use a non-approved location for backups. Here's how!
Feb 02, 2017 Yet, this very same feature causes network drives to dismount once the Mac goes to sleep. ? As I stated in the original post, this appears to be a longstanding problem that needs to be corrected in macOS, as many Mac users, particularly those in work environments, need to connect to servers, NAS, etc. That are not set up with Mac-centric.
The problem
The issue that makes Time Machine more difficult in terms of options for backup locations is that it requires use of Apple's proprietary HFS+ filesystem. Although I'm certain the HFS+ features that Time Machine uses for file versioning and linking could be 'mimicked' for use on other more open filesystems, the reality is that Apple chose HFS+ and supports that filesystem exclusively in Time Machine (in fact as of this writing Apple's new APFS isn't even supported for Time Machine backups as of yet).
![Shared Shared](/uploads/1/2/6/2/126297464/649625645.png)
Create a Windows share location
I won't go into detail on how to create a shared folder on a Windows PC but before you begin, you'll need to have a share created and accessible to your Mac that you want to run Time Machine on. For example, if you have a Windows PC named 'Server' and a network shared folder on the Windows PC named 'share', you'd be able to test for connectivity by doing the following:
- Start Finder.
- Click GO > Connect to Server.
- Enter smb://Server/Share where 'server' is the name of the Windows PC and 'share' is the name of the shared folder.
- Click Connect.
If you've properly set everything up, you'll be prompted to enter a registered user and password. Make certain to save those credentials to your keychain for the OS to automatically use those credentials for connecting to the share for future access. You should also see that share in Finder in your 'Shared' section and see the 'Eject' icon next to it since it is now mounted.
Create a sparsebundle image
We now need to create an 'image' file that will, in essence, pretend to be an HFS+ filesystem for your Mac to back up to.
![Use Use](/uploads/1/2/6/2/126297464/794980873.jpg)
- Start Disk Utility.
- Go to File > New Image > Blank Image.
- Rename the Save As to TimeMachine.
- Press the Down Arrow next to Save As.
- Select your mounted Share.
- Rename the Name of your sparsebundle.
- Select the Size of the backup location. Be generous. If you want to be able to at the very least backup the entire contents of a full hard drive, elect a size at least equal to your Macintosh HD drive size. As a word of warning, the size you choose will be the size of the disk space that will be immediately created on the remote share.
- Make certain that the Format is set to Mac OS Extended (Journaled).
- Click Save. This will take a while especially if you set a large file size.
- Click Done.
Mac Os Connect To Windows Shared Drive Windows 10
Make the remote share automatically mount
In order for this hack to survive reboots, we need to ensure that the remote share is automatically mounted when you restart your Mac. Here is a simple way to get this done. Some drawbacks of this method are that it only works once you've logged in and it won't work for other users of your Mac.
- Start System Preferences.
- Select Users & Groups.
- Select your Username.
- Click Login Items.
- Click the +.
- Navigate to and select your mounted share and TimeMachine.dmg file we created earlier.
- Click Add.
You may need to unmount the share before this can take effect but as of this moment, that share will automatically mount every time you reboot and log in.
Make Time Machine use the remote share and file
Finally, we're ready to make Time Machine see and use the Windows 10 share housing our sparsebundle file.
- Start Terminal.
- Enter the command sudo tmutil setdestination /Volumes/TimeMachine/ where 'TimeMachine' is the name you gave to your sparsebundle you created with Disk Utility.
- Enter your Password.
Check Time Machine
Now we just need to check that Time Machine sees the disk and is ready to use it for backups.
- Start System Preferences.
- Select Time Machine.
- You should now see that Time Machine has a backup location and Select Disk shows the proper name of the sparsebundle.
Final Comments
Yes, this is far and away from the simple 'just works' ideology that Apple is famous for. But if you have no other choice, it works for our Time Machine purposes. Do you have any comments or questions? Let us know in the comment section!
macOS Catalina
Main
We may earn a commission for purchases using our links. Learn more.
exposure notificationNational COVID-19 server to use Apple and Google's API, hosted by Microsoft
The Association of Public Health Laboratories has announced it is working with Apple, Google, and Microsoft to launch a national server that will securely store COVID-19 exposure notification data.
I have found the apparent source of the problem. Seemingly, having “Enable Power Nap” selected in the Energy Saver settings was forcing the network drives to dismount. I disabled that setting two days ago, and the network backups have properly worked the past two nights; the network drives also remain mounted as I can see when I come into the office in the morning. This behavior is counterintuitive given that the entire point of a Power Nap is to permit the computer to perform network based operations as per Apple’s own words:
“While sleeping, your Mac can back ip using Time Machine and periodically check for new email, calendar, and other iCloud updates”
Yet, this very same feature causes network drives to dismount once the Mac goes to sleep. ? As I stated in the original post, this appears to be a longstanding problem that needs to be corrected in macOS, as many Mac users, particularly those in work environments, need to connect to servers, NAS, etc. that are not set up with Mac-centric protocols.
Feb 2, 2017 3:37 AM