Closed sngz closed 7 years ago
Please provide the debug output from a vagrant up
. My guess is that guest additions are not available within the box but need the debug output to confirm.
seems like that was the issue, i thought the box I used had it preinstalled for some reason
@sngz Can you please provide details on how you got it to work?
@degan93 as mentioned by @chrisroberts guest additions was not installed.
@sngz thank you for your quick reply. What guest additions are you talking about? May I ask what you done to the box file to get the SMB connection to work?
@degan93 virtualbox guest additions
@sngz my apologies, I have misread this. My issue is with connecting to an EC2 instance.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Please note that the Vagrant issue tracker is reserved for bug reports and enhancements. For general usage questions, please use the Vagrant mailing list: https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Vagrant version
1.9.2
Host operating system
Windows 7
Guest operating system
VirtualBox with Windows Server 2016 Standard
Vagrantfile
Please note, if you are using Homestead or a different Vagrantfile format, we may be unable to assist with your issue. Try to reproduce the issue using a vanilla Vagrantfile first.
Debug output
N/A
Expected behavior
When trying to access C:\vagrant in guest machien it should open up the shared folder
Actual behavior
Location is not available pop up appears. C;\vagrant is not accessible. The network path was not found.
Steps to reproduce
References
none that i could find