I have a Mac Mini running macOS Catalina (10.15.7). We are running this version because we need to share drives and folders using AFP (not SMB) with remote users (via static IP from the InterWeb). This has worked fine for many years.
Now… When accessing this server remotely … I CAN NOT access some shared drives that ARE configured in System Preferences ➙ Sharing ➙ File Sharing ➙ Shared Folders AND I CAN access drives that ARE NOT configured in System Preferences ➙ Sharing ➙ File Sharing ➙ Shared Folders.
Obviously, these drives are configured somewhere in some networking config file for sharing that is NOT reflected in System Preferences.
What are these config files (for AFP / for SMB), and where are they located⁉️
Related
I am currently hosting my ASP.Net web application on AWS. I have searched for the best aws storage options for windows environment. I have found that aws File shares system FSx is suitable for our needs.
One of the required features in my app is to be able to create symbolic link on the network shared folder. On my local environment I have active directory and network shared folder. I have applied those steps to enable symbolic link on my pc with windows 10 and it works:
1- Enable remote to remote symbolic link using this cmd command:
fsutil behavior set SymlinkEvaluation R2R:1
2- Check if the feature is enabled:
fsutil behavior query SymlinkEvaluation
the result is:
Local to local symbolic links are enabled.
Local to remote symbolic links are enabled.
Remote to local symbolic links are disabled.
Remote to remote symbolic links are enabled.
3- apply this command for gain access to the target directory:
net use y: "\\share\Public\" * /user:UserName /persistent:yes
4- create symbolic link using this command:
mklink /D \\share\Public\Husam\symtest \\share\Public
It works fine on my local network with active directory.
On aws I have EC2 windows VM joined aws managed domain. The same domain I created the FSx with. I logged in to the machine with domain administrator. I gave security permission (share and security) to this uses on the shared folder using Windows File Shares GUI Tool.
When I try to create the symbolic link I get: Access Denied
mklink /d \\fs-432432fr34234a.myad.com\share\Husam\slink \\fs-432432fr34234a.myad.com\share
Access Denied
any suggestions? is there a way to add this permission in active directory?
It looks to me like mklink is not supported by amazon fsx. I can mklink to my heart's content on my ebs volume but not on the fsx. Also when I mount the share in linux ln -s test1 test2
ln: failed to create symbolic link 'test2': Operation not supported
I found a comment that said "in the GPO you can Change it in "Computer Configuration > Administrative Templates > System > Filesystem" and configure "Selectively allow the evaluation of a symbolic link" – deru May 11 '17 at 6:45." I don't think it will help because I can mklink on ebs.
This is a problem for me as my asp.net web app also uses mklink during it's setup. My solution is to use a windows container for my web app and then use docker-compose to put the links in to the FSx file system. I thought that I wanted to do the docker-compose build on the fsx volume. This was a terrible idea though because the ebs volume is way faster.
I was getting the same error messages reported above. I consulted with the AWS contacts available to the company I work for, and they confirmed that as of right now, FSx for Windows File Server does not support symbolic links.
I want to have shared folders between my computer on Arch Linux and a virtual machine with ReactOS, but I don't know where the folder appears in ReactOS.
Where does it appear?
Do it as you would do on Windows:
Install VirtualBox Guest Additions in your ReactOS VM
Define your shares in your virtual machine configuration (through VirtualBox interface)
Reboot your ReactOS VM
If you checked automount in the VirtualBox GUI, they'll be already available, mapped as a drive letter in the explorer. If you didn't, then either go to 'Network Places' to find them, or directly type the UNC path in the explorer address bar, or use the 'net use' command line tool
I would like to monitor and detect if a new file is created on a mounted folder in linux using c++.
I understand that inotify can be used only if the folder is local.
None of the common remote filesystems support notification.
The only general way to monitor a remote directory is via polling.
I am trying to create folders and file in Virtualbox shared folder from Host to guest.
But i get this error mkdir: cannot create directory : Protocol error.
Below are steps i performed to share folder
1:My host OS is Ubuntu and my guest is Ubuntu.
2:I attached a share folder to virtualBox VM
Folder Path:/DR/vault/config
Folder:config selected automount and make permanent.
3:In Guest OS i installed virtualbox guest additions
4:I am trying to mount folder on /mount/config path
I added entry in guest's /etc/fstab as
/config /mount/config vboxsf rw,uid=1000,gid=1000 0 0
Path gets successfully mounted after Guest reboot also i can see the files created in /DR/vault/config(Guest) to /mount/config(Guest) but i cant create folder or file in /mount/config (Guest)
Please suggest if anything is missing or if there is any other way.
In my case, I had the drive full, clearing some space on the drive solved the issue.
I have found this is a problem with filename lengths on DOS hosts.
I have been using VirtualBox VMs as a form of containerised environment for deploying to a JBoss server, having experienced far too many problems with Windows environments for said technology.
I was using a shared-directory with my host machine as I was trying to keep the virtual machine lightweight (i.e. keeping IDEs in the host machine), then checking code into the shared directory for deployment with Maven. However, maven was giving some odd errors when the directory length grew to over 255 characters. Try looking at your file absolute path (type "pwd") and seeing if it's longer than 255.
I've resolved this problem with the following:
On the guest machine, add your user to vboxsf group: sudo adduser username vboxsf
Restart the host machine.
My host OS is Windows, my guest OS Ubuntu.
This might be an indication that the folder does not have the correct permissions on the Virtualbox host.
E.g. my headless Virtualbox server is running as "vbox" user, so I had to give that user write permissions on the host folder.
I had a similar issue, turns out that for me it was the number of folders or length of path name involved in mkdir.
typically I had :
mkdir -p /projects/bot/node_modules/webpack/node_modules/uglifyjs-webpack-plugin/node_modules/uglify-js/node_modules/yargs/node_modules/cliui/node_modules/center-align/node_modules/align-text/node_modules/kind-of/node_modules/is-buffer
Manually I could create up to the last part of the path but not the 'is-buffer' folder
I am working in vagrant and my projects folder is a shared VM folder, maybe/probably windows' max path length is the reason.
I'm planning to install Visual Studio (for editing .aspx files) in a guest VM.
If I'm working in the Host computer, is there a way to open a file on that Host with a program in the Guest VM?
You could use the Shared folder feature for access to files on a host machine from Guest VM. To use this feature you should install the VMware tools on Guest VM. After setting up the Shared folder, you can access files on the host in a path like “\.host\Shared Folders\Test files”.
To send a command to open file on Guest OS from the host you could use vmrun utility, which helps you manage virtual machines from command line (for more detail see this official manual and examples in “Running Guest Applications”). On the other hand, you could just open a VM console and run script manually :)
In addition, I don't recommend to install Visual Studio on Guest VM. The Visual Studio will always execute faster on the host. Moreover, you will be more convenient to work with snapshots and few VMs. In this case, you could use remote debugging tools for debug and automatically deploy your application on Guest VM after build.