Given that these two pieces of advice conflicted, I thought to check it out. While SMB1 can be enabled, it is strongly recommended to not do so because of severe security risks. Out of the box, Windows 10 does not support the SMB1 protocol used on Time Capsule devices. ![]() They also suggest starting a command shell and typing ping #.#.#.# to make sure that your Windows PC can reach the Time Capsule. Since that's a really bad horrid computer virus, you really don't want to leave your computer open to that vulnerability.īut many postings I found suggest that you can manually Map Network Drive and give the IP address ( \\#.#.#.#\shareName) or give the server name ( \\server-name\shareName) to map the drive. Some point out that Windows 10 no longer supports (out of the box) NAS services based on the SMB1 protocol, because using SMB1 leaves your computer open to the Wannacry attack. A search for use apple time capsule from windows turns up a number of articles with differing opinions. 192.168.1.200/nas <- "nas" is where you put your username because the TC creates that shared folder name when you create the User account via the Disk tab in AirPort utility.Įither change your username to "nas", or change your destination folder to //192.168.1.200/airp-account-user.Unfortunately it's not hard to find incorrect advice on this issue. It seems the username and the share in your IP/Destination_folder have to be the same, in your case: Save and reboot to make sure it re-mounts. If you want it to automount each time you reboot your *nix box, add an entry to your /etc/fstab (but I find that confusing), so I just added a cron task to re-mount at reboot using: crontab -eĪdd into your crontab the whole mount command above. Then try to mount it with this: mount -rw -t cifs //IP/username //mnt/timecapsule/ -o username=username,password=password,sec=ntlm,vers=1.0 On your *nix box, create a directory where you'd normally mount stuff, i.e. Once it's restarted, make sure you can ping it from your *nix box. Go to your TC, into Disk, click on Account and create a username and give it a password. It would be great if I could get this thing up and running! Mount.cifs: permission denied: no match for /home/curruser/airport found in /etc/fstab When I try to use this mounting command without sudo (in an attempt to avoid the changing of ownership), I get the following error: I also tried adding rw as parameter, but this doesn't changes anything. Sudo mount.cifs //192.168.1.200/nas /home/curruser/airport/ -verbose -o username=airp-account-user,pass=airport-account-passw,sec=ntlm,vers=1.0,gid=$(id -g), uid=$(id -u),forcegid,forceuid, file_mode=0777, dir_mode=0777 After remounting the disk the same thing happens all over again. When I unmount the disk and then change the owner, it works like normal and the owner is back changed to curruser. I tried changing the owner of the folder, (sudo chown curruser /home/curruser/airptc), although this doesn't generate any errors it doesn't do anything. ![]() So after mounting, I can see and access the files in the target folder, but it is only readonly. ![]() ![]() The problem I have is that when I mount the disk to a local folder, that the owner of the folder always changes to root. I recently got a Apple airport time capsule and I am trying to use the disk as a NAS.
0 Comments
Leave a Reply. |