How to get the network path of local machine c drive using powershell.
like in my local machine "\Desktop-rgh5sj2\c", which i got by manually
by This pc --> Map Network Drive --> from browse selecting the local c drive.
Related
I currently purchased Synology's ds220+ model and am using it as a NAS Server.
The line is connected to the LAN port of the router to which the WAN line is plugged, and the end is connected to the NAS.
In this situation, I wanted to set up a NAS server to be used externally, not on a local network.
So I even set up WebDAV Server, DDNS, and port forwarding on the router.
To test this, I created a NAS server directory through RaiDrive in a Windows environment.
From the created directory, I tried to upload files to a folder with read/write permission and confirmed that it was working normally.
However, the problem occurred in MacOS.
In Finder, a server folder was created through the "Connect to Server" option, and a file upload was attempted, but an error such as the attached picture occurred in all types of files.
Could you tell me if there is a problem with the way MAC creates the server folder?
Idea: Your OS doesn't support SMB:
Download an FTP or SMB client. (FTP: E.g.: Filezilla)
Idea: A friewall is blocking it:
Check your anti-virus-program
Other Problem:
Use an USB Stick & NAS USB Copy
or upload it via DSM File Manager
Open NAS IP-adress via Safari/Firefox/Chrome
Log In
Open File Station / File Manager
Search folder
Click [Upload]
Choose the file from your PC
Finised
I have a NiFi instance running on my local Windows workstation.
I want to copy a flow file to a shared network drive: \\sharedpath\files\destination
I am able to use the PutFile processor to copy the file to C:\Temp\Files for example on my C drive.
But PutFile doesn't work with Windows shared network path such as \\sharedpath\files\destination.
The error message is linked here: https://i.stack.imgur.com/jiK5T.jpg
I seem to be running the least supported combination of docker. Im running on a windows host machine and a windows container.
I want to mount C:\temp -> C:\temp
I have tried
docker run ... -v C:\temp:C:Temp
docker run ... -v C:/temp:C/:Temp
docker run ... -v //C:\temp://C/:Temp
Im supposed to go to docker settings "Shared Volumes". But that is not available for Windows containers
When I try to read from that directory in my application, the directory does not exist
I too was not able to mount C drive inside windows container to my
host OS C drive. The solutions given on mounting drives seems to be
related to Linux containers running on windows which is not expected
here.
There is a workaround I did to access the host C drive from inside the
container and copy the files to a folder outside the container and
watch them in explorer(If that is the behavior which solves you
purpose). Below are the steps I performed.
1) docker exec -it container(name/id) powershell (open powershell
inside container)
2) net use X: \SERVER\Share (X is the name of the network drive. You
can choose any name. SERVER is the IP address of your host machine.
Share is the folder name which is present in the host machine. In your
case it is c:\temp) Example: X:\ \XXX.XXX.XXX.XXX\c$\temp You will be
prompted to enter your username and password
3) Once you have this setup, you can browse your network drive (X:).
Anything on your host temp folder will be accessible inside your
container. You can copy the files and folders to and from this network
drive and it would be visible in your C:\temp folder on your host
machine.
Hope this helps!
I have a remote drive (on an SBS 2011 server) mounted on my iMac BUT each time I reboot the iMac I have to relogin into the remote drive. How can I make this automatic?
I have come across some AppleScript approaches but none of them seem to work. E.g.
do shell script "mount_afp afp://username:password#192.168.100.2/Backups123 /Backups456"
Where username/password are valid for the remote server/folders, 192.168.100.2 is the IP of the Server and /Backups456 is the name of the mounted volume on the iMac.
Any ideas?
I am using puphpet.com tool to set up Vagrant boxes.
Now , I am able to ssh to it and open the IP on the browser but I can not get to access the VHost I set up earlier through puphpet.
I have edited my hosts file (/etc/hosts ) "using OSX" to serve the IP 2.168.56.101 to lab.dev. Now it works fine but I can not access the virtual machine on the guest machine !!!!.
I am using PHP Laravel framework and I need to access the server name which points to /var/www/lab.dev/public/. I would appreciate very detailed answer as I am really new to all of this
Detailed Instructions
Visit PuPHPet.com to build your Vagrantfile.
Configure your Shared Folder Pairs. This is under "Deploy Target > Locally".
Let's assume this directory structure on your OS/X machine:
/Users/unrivaled/Documents/laravel-project (project files go here)
/Users/unrivaled/Documents/laravel-project/public (the web root files)
Folder Source represents the location on your main computer (the "host" operating system), where your source files reside; for example: /Users/unrivaled/Documents/laravel-project The Folder Source must be on your OS/X machine, exactly where your Laravel files are.
Folder Target represents the location on your virtual computer (the "guest" operating system), where you want Vagrant to make them visible to the web server; for example: /var/www/lab The Folder Target can be anywhere that Apache or Nginx, in the virtual machine, can reach it.
Folder Source (local machine) == Folder Target (virtual machine)
/Users/unrivaled/Documents/laravel-project (local machine) == /var/www/lab (virtual machine)
Configure your web server. Your Server Name can be anything you want; in this example, let's use "lab.dev". Configure your Server Alias; in this case, use "www.lab.dev." Your Server Name (or an alias) must match your entry in your /etc/hosts file; see below. Configure your Document Root. This is the folder on your virtual machine where your website files will go and the files that will be served by Nginx or Apache. This value must be at, or below, the Folder Target defined from Step 4; for example, /var/www/lab/public.
Notice in the example how we are giving the web server access to /var/www/lab/public? This actually refers to /Users/unrivaled/Documents/laravel-project/public on your local OS/X system, thanks to the "Shared Folder Pairs" configured in Step 2., above.
Generally, configure everything else in PuPHPet as you see fit.
Run vagrant up to get your virtual machine up and running. If it doesn't work at this stage, you need to resolve any problems before going on.
Determine your virtual machine's IP address. Use vagrant ssh to log into the virtual machine, and then ifconfig should work for this. Do not rely on the IP address defined in PuPHPet. Your virtual machine provider will likely override this value, and you need to know the actual, in-fact IP address.
On your main host computer (not the virtual machine), edit your /etc/hosts file: sudo nano /etc/hosts, adding the server's IP address, followed by the Server Name (or a Server Alias) defined in Step 5, above.
How It Works
Once you have a working web server using the settings in this example, you can view your website by going to lab.dev. Your browser in OS/X will resolve lab.dev to the proper IP address of your server by way of the /etc/hosts file. It then requests your web page from that IP address, where the server matches the requested resource, "lab.dev," to the appropriate Server Name or Server Alias that matches. The files in the Document Root for that server name (/var/www/lab/public) will be processed by the web server.
In summary, your server's IP address in the local /etc/hosts file matches your server's IP address in the virtual machine; your server's name in the local /etc/hosts file matches your Server Name (or Server Alias) in the web server on the virtual machine; the path name to your project source files on your local computer (Folder Source) maps to the Target Directory on the virtual machine; and finally, a subdirectory of that target directory (public) corresponds to the Document Root for the web server.