![]() ![]() This is a more general workaround than the one I used and should work in many more situations, including with Ubuntu on a bare machine and not in a VM. I considered, if necessary, modifying the systemd configuration files to make nmbd not start until network initialization was done. This workaround was fine for my case but might not be sufficient in all cases. Click the + (plus) icon to add the shared folder/directory. Or simply, from VM interface menu, click on Devices > Shared Folders > Shared Folders Settings. ![]() With this change, nmbd came up properly and all my problems disappeared. To access VirtualBox Shared Folder settings, highlight the vm on VirtualBox interface and press Ctrl+s to launch the VM settings. For Linux kernel version 4.0 or later, enter the command /usr/bin/vmhgfs-fuse -h to list the available options. Enter the command /sbin/mount.vmhgfs -h to list the options. My workaround was to increase the number of threads available to Ubuntu to 4. For Linux kernel prior to version 4.0, you can use VMware-specific options in addition to the standard mount syntax. ![]() In addition, the VM had only been given one thread which slowed things down even more. The reason for this situation was that Ubuntu was running in a VM and hence was taking longer than normal to initialize and the network was not yet available when nmbd tried to initialize itself. It was crashing, because it needed a working network before completing its' initialization. The component nmbd in Ubuntu that actually publishes shares via Netbios was crashing and was unable to report the existence of the Samba shares. However, I had to overcome a Linux bug that is at least 10 years old and was reported to Fedora in 2009. I solved this problem by implementing Samba in Ubuntu and connecting to the Samba shares from Windows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |