nanobox-io / nanobox

The ideal platform for developers
https://nanobox.io
MIT License
1.61k stars 89 forks source link

Nanobox will not accept user password to mount onto Virtualbox #663

Closed Jarmahent closed 6 years ago

Jarmahent commented 6 years ago

Kevin's(me) password is required to mount a Windows share. (must be your Windows Live password if linked) Windows Password:

I then put the correct password. Multiple times and it always says  \ Mounting codebase : Then proceeds to ask me again.

Jarmahent commented 6 years ago

Fixed, running: nanobox config set mount-type native made nanobox not ask me for password anymore

raulingg commented 6 years ago

Working. Thanks

danhunsaker commented 6 years ago

As a side note, this is a workaround rather than a fix. The native mount-type is slower than the netfs mount-type, usually noticeably, so it has some tradeoffs.

The correct fix involves ensuring a few things are properly set up on your development system. First, you must use a password to log in to your computer - this is just good security practice anyway, but is also required by Windows to allow access to file shares on the host. Second, you need to mark the network used by the Nanobox network bridge (a TUN/TAP Adapter) as a Private network, so that Windows File Sharing will allow the Nanobox VM to actually see your shares. Then, you also need to ensure that file sharing is actually enabled at all, which can be a relatively involved process better explained by tutorials already elsewhere on the Internet. If all of these are currently set up correctly, then there's another problem somewhere that we'd have to collaboratively track down.

rflash95 commented 6 years ago

I found a solution. You must allow file and printer sharing and file and printer sharing over SMBDirect on the private network. nanoboxo

If the TAP adapter is still a public network because of an unidentified network, you can change it to the Local Security Policy -> Network List Manager Policies -> unidentified network -> Location Type -> select Private. local security policy

private network