Need assistance with Ubuntu Server inside a virtual machine. Setting up a file share is the goal.
Need assistance with Ubuntu Server inside a virtual machine. Setting up a file share is the goal.
I’m working with an Ubuntu Server inside a virtual machine to create a file-sharing solution. I need it to be reachable from both the Windows host and other Windows machines over the internet, and I want to set up regular backups from the VM to another drive on the host for extra safety.
I’ve created a user with elevated sudo rights, enabled SSH, updated packages using apt, installed Docker, and tried to install Samba. I managed to locate the smb.conf file and adjust its settings, but couldn’t add users, create test files, or access anything on the VM or host. The service appears to start correctly in Docker but not when installing via standard apt.
I’ve downloaded and removed Samba multiple times using both Docker and the default sudo apt install command. I can confirm it’s running in Docker, yet not through the usual package manager. I’m unable to create a dedicated Samba folder, test files, or allow access from Windows devices. This issue also prevents me from testing connectivity over WhiteSky, which I’m using as an intermediary between my ISP and the local network.
I’m open to trying a slightly older Ubuntu Server LTS version, but I don’t want to switch to Raspberry Pi OS or a graphical interface—I prefer learning through the terminal first. I’m also curious about alternatives for secure, reliable backups, preferably local ones, and I’d appreciate step-by-step guidance.
Please let me know how to proceed.
Was es dir gelungen, dich mit deinem VM zu verbinden? Es könnte ein Problem mit der Netzwerkkonfiguration deiner VM sein.
I didn’t try because it wasn’t necessary. Still, my router identified the VM as a wired connection, and I was able to reach 1.1.1.1 via the Ubuntu terminal with minimal lag—just under 0.6 milliseconds compared to Windows.
If the VM lacks a headless setup, consider alternative methods beyond SSH. The only reliable approach to manage Ubuntu servers is through the command line interface, which you access via SSH. Unless you're working with the virtual machine's graphical interface, stick to SSH—it's the proper method for server administration, as most systems aren't run directly from your desktop.
It seems you're validating your assumption. Test it now to check functionality. If issues arise, your configuration might be affected by a NAT behind your host.
Change the network configuration to Bridge instead of NAT in VirtualBox.
It took a moment to figure this out. SSH functions locally on the LAN but fails when trying the internet. The network settings are linked to a bridged adapter via the motherboard's built-in Ethernet controller.