how to copy to shared folders from command-line in vmware-workstation?

command-line-interface vmware-workstation copy network-share

5,279

ok, after much pounding my head, i found the answer. it actually had nothing to do with the vm, the network, or permissioning. turns out it was a short 8.3 format name problem. as can be seen in my question i was calling 'shared folders' without quotes and without short syntax. to correctly call shared folders from within a vm (or otherwise) from the cmd line, you must wrap up the directory call in quotes as below:

dir "\.host\shared folders"

works!

5,279

Hecter

Updated on September 17, 2022

Comments

Hecter almost 2 years
I've been trying to access my shared folders from the command line in my virtual machine with no luck. I've stumbled across a couple of references to using net use to establish a virtual drive, but i can't get this to work correctly:
```
net use z: \\.host\y (where y is my shared folder)
net use z: \\.host\shared folders\y
```
Neither of these works. Any pointers?
Admin almost 14 years

no, i'm going to be doing it on regular intervals. this is for a batch file for backing up files to another drive in shared folders which is on the same machine which is hosting the vm.
Nikolaidis Fotis almost 14 years

ok then. but the question remains :> were you able to access the shared folder from another machine ? That's a question to determine if the problem is located in VM's configuration or in the connection between VM and host machine.
user48838 almost 14 years

Which type of networking is set up on the guest - bridged or NAT? If it is setup for NAT, then the host IP in that arrangement is the NAT default gateway/DHCP server.
smoothgrips almost 14 years

yes, it's setup as nat, the default gateway address produced the same error: 67.
Admin almost 14 years

i've never tried accessing the share from another machine. the share is enabled from directly within vmware workstation solely for that particular machine.
user48838 almost 14 years

Is the "host" machine that you are trying to reach actually another "guest" virtual machine which is also on a NAT setup? If so, you will need to consider changing it over to Bridged or creating and "internal" network (via Internal virtual NICs) between the virtual machines.