VOGONS

Wfw 3.11 - mapping to NAS using SMB1?

Topic actions

First post, by my03

Posted on 
User metadata
Rank Member
Rank
Member

Hi,

During the weekend i managed to map several of my old W98 based laptop to my QNAP nas by altering the Samba version down to version 1 (yes, I know the risks, but its not facing the internet, its only for internal use) and making sure that the login user/pwd corresponded with a user/pwd defined for a share on the NAS. All good and dandy.

Then i tried to replicate the same from another laptop that runs Wfw 3.11, using TCP32B, and while i can actually see the NAS shares (including the one that i permitted access to for the particular user that i defined in WfW), whenever i try to connect to it, it won't allow it.

I guess there is something here that is misaligned. Did anyone here manage to map a share and make it accessible via Windows 3.11? How did you do it?

Reply 1 of 6, by jakethompson1

Posted on 
User metadata
Rank l33t
Rank
l33t

Since you're using a username and password, in addition to de-hardening the server to SMB 1, you might also have to de-harden the server's password hashing settings. See the "lanman auth = yes" and "ntlm auth = yes" in smb.conf. You might also have to rerun smbpasswd to set the LM hash for the user. Since LM is useless security, you might set up a separate share with guest access allowed just for WfW 3.11 purposes.

Reply 2 of 6, by maxtherabbit

Posted on 
User metadata
Rank l33t
Rank
l33t

I suspect that Jake is onto something here, I do have both DOS and WfW3.11 clients connected to my samba share but I also have guest access enabled.

BTW - make sure you add the config directive "strict sync = no" to your samba config or else your 98 machines won't properly view the shares. They will map them fine either way but you will have problems actually accessing the files.

Reply 3 of 6, by nali

Posted on 
User metadata
Rank Member
Rank
Member

What do you do to allow Samba access from Dos and WFW ?
I never had any success, so I use a small virtual Debian Etch in a VM just for Win98 access on my "server" ...

Reply 5 of 6, by maxtherabbit

Posted on 
User metadata
Rank l33t
Rank
l33t
nali wrote on Yesterday, 02:06:

What do you do to allow Samba access from Dos and WFW ?
I never had any success, so I use a small virtual Debian Etch in a VM just for Win98 access on my "server" ...

server min protocol = LANMAN1

Reply 6 of 6, by vutt

Posted on 
User metadata
Rank Member
Rank
Member
schmatzler wrote on Yesterday, 04:12:

I just run a Raspberry Pi with Debian 12 and this setup:
https://gist.github.com/tinue/9d9ce9c09e9e771 … 9b27f6d0e859c4e

Cool! What I have done is to create minimum Docker configuration. I'm running docker infra with my TrueNAS. For added security I set up smb in read-only mode, since it's my main workflow getting stuff into retro PC, but if I need to write something back I also added FTP server to docker image.
I'm rather paranoid so I have actually dedicated NIC in my main NAS. So my main network and retro network are physically separated. I was thinking about legacy Linux VM-s but running minimum Docker will reduce potential attack surface. No need to be concerned about other full op.system security holes. Although your Bookworm will be supported till 2028, with extended support till 2033...
Docker repo: https://github.com/vutt-code/retrosamba416

Go to top of page Go to top of page
Back to General Old Hardware
Close window
Close window