On Sun, Mar 02, 2025 at 11:26:38AM +0000, Rowland Penny via samba wrote:> On Sun, 2 Mar 2025 03:29:17 -0600 > Mike Brown via samba <samba at lists.samba.org> wrote: > > > What is strange is that it is working fine with V3(?) under Fedora 27. > > The only difference, that I know of, is V4 under F41. > > It isn't strange, it is to be expected. > If I remember correctly, fedora 27 came with Samba 4.7.9 and the > default for 'server min protocol' was 'LANMAN1' > This was changed at Samba 4.11.0 to default to 'SMB2_02'Thanks for the info.> This means that if your Win7 machine is only using SMBv1, then it could > connect to the fedora 27 machine, but it would not be able to connect > to fedora 41, where SMBv1 is turned off by default.I need to find out what it is.> > That said, I am thinking about enabling the Win7 nfs client and use it > > instead. I haven't configured a Linux box to export files via nfs in > > ages. :-) > > Is there a working NFS client for Windows 7 ? I know there is one for > the latest Windows. It will probably be easier to get Samba working.Supposidly. A search provided instructions on how to enable it. I've not tried yet. MB -- e-mail: vidiot at vidiot.com | vidiot at vidiot.net /~\ The ASCII 6082066843 at email.uscc.net (140 char limit) \ / Ribbon Campaign Visit - URL: http://vidiot.com/ X Against http://vidiot.net/ / \ HTML Email GEORDI: "Data, could you try being a little more positive..." DATA: "I hope we die quickly!" (Star Trek: Picard - 4/13/23)
We had a similar issue with an industrial robot built on Win 7. Our solution was to add another VM with SMB2 as allowed minimum client for it's file share. No changes were required on the Win client (not sure which SP it is built on though) On Mon, Mar 3, 2025, 03:47 Mike Brown via samba <samba at lists.samba.org> wrote:> On Sun, Mar 02, 2025 at 11:26:38AM +0000, Rowland Penny via samba wrote: > > On Sun, 2 Mar 2025 03:29:17 -0600 > > Mike Brown via samba <samba at lists.samba.org> wrote: > > > > > What is strange is that it is working fine with V3(?) under Fedora 27. > > > The only difference, that I know of, is V4 under F41. > > > > It isn't strange, it is to be expected. > > If I remember correctly, fedora 27 came with Samba 4.7.9 and the > > default for 'server min protocol' was 'LANMAN1' > > This was changed at Samba 4.11.0 to default to 'SMB2_02' > > Thanks for the info. > > > This means that if your Win7 machine is only using SMBv1, then it could > > connect to the fedora 27 machine, but it would not be able to connect > > to fedora 41, where SMBv1 is turned off by default. > > I need to find out what it is. > > > > That said, I am thinking about enabling the Win7 nfs client and use it > > > instead. I haven't configured a Linux box to export files via nfs in > > > ages. :-) > > > > Is there a working NFS client for Windows 7 ? I know there is one for > > the latest Windows. It will probably be easier to get Samba working. > > Supposidly. A search provided instructions on how to enable it. I've > not tried yet. > > MB > -- > e-mail: vidiot at vidiot.com | vidiot at vidiot.net /~\ The ASCII > 6082066843 at email.uscc.net (140 char limit) \ / Ribbon > Campaign > Visit - URL: http://vidiot.com/ X Against > http://vidiot.net/ / \ HTML Email > GEORDI: "Data, could you try being a little more positive..." > DATA: "I hope we die quickly!" (Star Trek: Picard - 4/13/23) > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
On Sun, 2 Mar 2025 20:43:36 -0600 Mike Brown via samba <samba at lists.samba.org> wrote:> On Sun, Mar 02, 2025 at 11:26:38AM +0000, Rowland Penny via samba > wrote: > > On Sun, 2 Mar 2025 03:29:17 -0600 > > Mike Brown via samba <samba at lists.samba.org> wrote: > > > > > What is strange is that it is working fine with V3(?) under > > > Fedora 27. The only difference, that I know of, is V4 under F41. > > > > It isn't strange, it is to be expected. > > If I remember correctly, fedora 27 came with Samba 4.7.9 and the > > default for 'server min protocol' was 'LANMAN1' > > This was changed at Samba 4.11.0 to default to 'SMB2_02' > > Thanks for the info. > > > This means that if your Win7 machine is only using SMBv1, then it > > could connect to the fedora 27 machine, but it would not be able to > > connect to fedora 41, where SMBv1 is turned off by default. > > I need to find out what it is. >I installed win7 in a VM over the weekend, I just created a local Windows user and did not join it to the domain. I then created a share on a Unix domain member, which was running Samba 4.21.3 and with 'disable netbios = yes' set (so definitely no NetBIOS): [testshare] path = /srv/test read only = no I set the permissions, as a test, to '0777': ls -lad /srv/test drwxrwxrwx 3 root root 4096 Mar 2 13:23 /srv/test Connected (in Network) from the win7 machine: \\192.168.1.114\testshare Entered my domain username & password when prompted, I was logged in and was allowed to create a directory, checking on the Unix domain member gave this: ls -la /srv/test total 16 drwxrwxrwx 3 root root 4096 Mar 2 13:23 . drwxr-xr-x 3 root root 4096 Mar 2 13:17 .. drwxrwxr-x+ 2 rowland domain users 4096 Mar 2 13:22 testfolder So I created another share, set 'map to guest = bad user' in 'global' on the server and connected to the share as an unknown user and that worked. So it is possible, it looks like something on the OPs win7 isn't set up correctly. Rowland