Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.ubuntu    |    I preferred Xubuntu, seemed a bit faster    |    134,474 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 133,383 of 134,474    |
|    Paul to pinnerite    |
|    Re: Samba and Windows 10    |
|    17 Jul 23 19:21:35    |
      XPost: alt.os.linux.mint, alt.os.linux.mageia       From: nospam@needed.invalid              On 7/17/2023 4:05 PM, pinnerite wrote:       > I cannot get Windows 10 to see samba shares on my reincarnated Mint 21.1.       >       > I have tried every combination of min and max protocols.       >       > Windows XP on the same configuration does see the samba shares.       >       > I have come to the conclusion that I previously must have been using an       earlier version of VirtualBox.       >       > I had been using version 7.0.8 on this rig but it had annoying       characteristics so I went back to 6.1.12. I have nothing earlier than that.       >       > If anyone happens to be a VBox user and knows the answer. Plesase share.       >       > I can carry on using VBox's shared directories but it is a niggle.       >       >              First you have to do               ipconfig              in Windows 10 and see what your VirtualBox has netted for an IP address       from the DHCP on your router (or not). You can run with default "NAT"       for the VBox choice or you can try "Bridged".              Without discussing all the security implications, these       are the settings in the Linux Host (I'm using LM212 Victoria Cinn for test       here).       I did a "sudo apt install samba", before setting up my LM212 share. And,       I can see my Windows share, which for once, didn't put up a fight. I didn't       set up a test share in my home, and put it under slash instead. Just to get on       with it.               /etc/samba/smb.conf               ...        workgroup = WORKGROUP               server min protocol = NT1        server max protocol = smb3        client min protocol = NT1        client max protocol = smb3        client lanman auth = yes        ntlm auth = yes              That should be enough to make a VBox WinXP and a VBox Win10 work.       Previously, there was an authentication issue (get the dialog,       enter the details of the Win10 box, and get rejected). It's possible       the auth lines helped.               Paul              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca