Windows 10: Samba broken on Fedora 31 VM

Hi folks These issues are raised here because some people might think it's a VMWare or Windows problem -- in this case both Ms and VMware seem entirely innocent for once !!!. Those trying latest updates to FEDORA as a VM (Fedora 31 kernel 5.X.X) will probably find SAMBA doesn't work --doesn't matter the SMB protocol -- seems to be broken. Other distros work OK as VM's but some fail to give 1920 X 1050 Screen resolution without a lot of hassle -- probably due to errors in the Wayland video manager rather than the older XORG. Funny how this resolution fails as I would supect currently it's probably the most common one around (1080p HD). XRANDR temporarily fixes it but immediately reverts back to a tiny screen again. HOST Windows 10 Workstation pro running VMWare WKS rel 15. Release of W10 is latest Fast ring release but I suspect it's a generic problem. I suspect for the display problems this isn't Windows or VMWare's fault -- SAMBA problem is definitely with Fedora -- the server edition based on RHEL server 8 -- Centos 8 works OK with samba though and the screen resolution is OK as you can select at login time whether to use Wayland or XORG (just click the little cog by the login user screen). Cheers jimbo

:)

 

Samba broken on Fedora 31 VM

Hi folks

These issues are raised here because some people might think it's a VMWare or Windows problem -- in this case both Ms and VMware seem entirely innocent for once !!!.

Those trying latest updates to FEDORA as a VM (Fedora 31 kernel 5.X.X) will probably find SAMBA doesn't work --doesn't matter the SMB protocol -- seems to be broken.

Other distros work OK as VM's but some fail to give 1920 X 1050 Screen resolution without a lot of hassle -- probably due to errors in the Wayland video manager rather than the older XORG. Funny how this resolution fails as I would supect currently it's probably the most common one around (1080p HD). XRANDR temporarily fixes it but immediately reverts back to a tiny screen again.

HOST Windows 10 Workstation pro running VMWare WKS rel 15. Release of W10 is latest Fast ring release but I suspect it's a generic problem. I suspect for the display problems this isn't Windows or VMWare's fault -- SAMBA problem is definitely with Fedora -- the server edition based on RHEL server 8 -- Centos 8 works OK with samba though and the screen resolution is OK as you can select at login time whether to use Wayland or XORG (just click the little cog by the login user screen).

Cheers
jimbo

 

Samba broken on Fedora 31 VM

Hi there
@roy111

Haven't tried that yet -- I usually only run Linux VM's from Windows Hosts !! although it's a thing to try -- these installs only take a few minutes to do (usually about 10 - 15 mins Max to see if the things boot and get any probs like screen issues.)

Installing Linux distros -- at least basic base stuff isn't like Windows --they either install quickly and boot or fail so only about 10 - 15 mins time needed so I'll have a go on Sunday Morning for you.

Samba though must work --otherwise it's a real NO NO / show stopper for me -- and unfortunately I have to have SMB1 working -- older KODI / Firestick / android TV's need SMB1.

Fedora 31 seems to have added a whole lot of extra protection -- I know this can sound good but sometimes especially on HOME secured LAN's for sharing files from a server there's sometimes TOO MUCH security --I'm not trying to keep the CIA out !!!!.

Current Linux Host I could try this on is ARCH Linux - kernel 5.5.3
Samba version 4.10.10

Cheers
jimbo

 

Fedora dual boot not showing after win10 installation

I had Fedora 31 & win7 on my system. After installing Windows10 pro, Fedora dual boot disappeared & directly win10 loading. How to get back dual boot? Win10 have dual boot?