SMB synced folder fail on Windows 8.1 host #4823
Labels
Comments
|
Looks like it might be related to my issue #4806 |
|
In addition, I boot up the vm with default sharing, and run the command, I got, and after install the cifs-utils, it becomes, The user "smb" is created on Windows and the share folder is set up for sure. |
|
I have the exact same problem, I think. VirtualBox's file sharing is horribly slow and the lack of NFS is an ongoing issue. This is damaging my productivity 😦 Here's my logs: |
|
Hi. Any changes on this? I have the same problem after installing PowerShell 3.0. |
|
Same problem for me... |
|
Has everyone tried enabling lower level logging? When I have had these issues (two separate times with similar errors but different causes) I was ultimately able to get to the root of it by enabling logging. Just set an environment variable before you run the command: I know |
|
I tried that with the debug mode and got: |
|
Do you happen to be using a computer that's connected to a windows domain? i.e. Is it a work computer? Also, do you happen to use VPN? |
|
Yes, it's a work computer using a domain but as far I know there is no VPN in use. |
|
Has it ever worked for you in the past? If so, then it's possible that you might be isolated behind some sort of firewall. I know in my case it worked when directly connected (ethernet) and not over Wifi, or, over VPN. Here are a few suggestions:
I'm interested to see what ends up working for you; that permission denied error is a bit vague. |
|
No, it never worked before.
|
|
Obviously I'm pretty clueless on how to help :D Since the next question is a bit of a shot in the dark: You do have a password set and frequently type the password to log on, right? And you're positive the IP that it's attempting to connect to is your IP? |
|
I had the same problem this morning (my time, obviously :-)). The way that I seem to have fixed it so far is the following:
I did all three of these at once, so I'm not sure which of these steps is the real problem. You can try them out and let us know. |
|
@patricknelson: You gave great hints and I really appreciate that! Yes, password is frequently typed. |
How to reproduce
add this line to Vagrantfile: Bug n°1: vagrant up freeze during "clearing forward ports"I can't get the logs back but the solution was the one describe in #3139 Bug n°2: unable to mount cifsI got the exact same problem as describe in previous comment ( #4823 (comment)) and tried the same things but it was a dead end I found the solution by commenting this line in
|
|
Thanks @francisoud The change in your pull request worked for me. Host: Windows 7 Pro |
|
I may be a little late to this but I was getting a permission denied/mounting read-only, can't mount read only error. How I solved it was to use [email protected] when it asked for my username and it worked like a charm. If someone sees this and directs me where to document this it would be appreciated. Thank You. |
|
Sorry for ask this thing here instead search, but, how do I apply this patch to my vagrant installation ? Should I compile the whole vagrant thing? |
|
Just tested this and this is all fixed from the above PR. Thanks! @killua99 a new Vagrant release will come out later this month. |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Host: Windows 8.1 Pro
VM: Ubuntu Trusty 14.04 LTS x64
Vagrant: 1.6.5
Virtualbox: 4.3.18
Tried on both cygwin and powershell, and got the same error.
The text was updated successfully, but these errors were encountered: