MS-DOS 6.22 SMB Share

[Martin616]

Hi,
i have MS-DOS 6.22 VM which is in the same subnet as the FreeNAS 11.2. I can ping the FreeNAS from the DOS machine.
The FreeNAS has 2 shares which are accessable from normal (windows 7 and windows 10) clients.
Trying to mount the share on the DOS machine results in "Error 58: The network has responded incorrectly."

Does anyone know what needs to be configures at the FreeNAS to make it accessable from the DOS machine?

Thanks in advance!

 

[sretalla]

Look here under section 11.4, see the Orange Warning box.

It's my assumption that you're going to be using SMB1.

 

[Martin616]

Thanks for that quick answer!
I made the changes but there is no change in the behaviour of the MS DOS client.
Its still "Error 58: The network has responded incorrectly."
Does someone have advanced knowledge of MS DOS 2.66? Maybe the problem is there...

 

[sretalla]

What's the command you are using to connect?

Are you specifying the user as part of that command?

 

[Martin616]

No im not specifying the user. Im using:
net use i: \\ndxxxx\prod

I added the hostname ndxxxx in the hosts file with the corresponsing IP. Im able to ping that host.
And this share is accessable from Windows 7 and Windows 10 clients

 

[sretalla]

Have you also updated the LMHOSTS file? (for SMB1 this will be important).

Also, I suspect specifying the user will make a difference.

net use /USER:DOMAIN\usr1 i: \\ndxxxx\prod

 

[Martin616]

The command with /USER: DOMAIN is not known on the DOS. And its not appearing on the net use help pages.
I also updated the LMHOSTS file.

Why should i use /USER: DOMAIN\usr1? Where is this user "usr1" created and located?

 

[sretalla]

OK, so you're on an unsupported client, therefore can't expect this to work, but we can continue to discuss it.

I gave you the command with DOMAIN\usr1 as a template for you to use your own DOMAIN and user in place of those. (I didn't want to use "user" again, since it's part of the command, so I chose usr1... sorry for not spelling all that out before... but seems it doesn't matter if you can't get a client that will authenticate).

You may need to play around with the SMB share and essentially open it up for no authentication (I guess some auxiliary parameters may get you to that somehow... I have never wanted/done that, so don't know about it).

 

[BjörnWagner]

Hello,

I've the same problem. I want to mount a freenas smb share on a vintage msdos box.
Even when I activate smb1 support I get "error 58 the network has responded incorrectly"
when I try to mount the share.

Has anybody found a solution for this problem?

I'm running FreeNAS-11.2-U8.

Best regards,
Björn

 

[sretalla]

Have you enabled NTLMv1 Auth and SMB1 protocol?

 

[swissroot]

never thought that someone is still using DOS...

I‘ve searched through my old notes where memmaker and doublspace was in use.

due to the new samba versions I would check those settings in your conf. May it can point in the right direction. Also keep in mind with all those settings you open up some really bad things on your machine in a security perspective.

Mapping with user and password:
net use i: \\server\share <user> <password>

Samba config:
lanman auth = Yes
client ntlmv2 auth = no
client plaintext auth = Yes
server signing = disabled

Authentication with old clients:
By default, later versions of Samba do not create the LANMANAGER hash when a user account is created unless lanman authorisation has been enabled.
Check whether the user account has a LANMAN hash with 'pdbedit -L -w'. 'man 5 smbpasswd' should help with the layout of the output. If not, you will likely need to delete and remake the user account using pdbedit.

not sure if it helps or works, but this where some things we used at the time of linux smb and some old dos telex gateways.

 

[adrianwi]

Upgrade to Windows 3.11

 

[anodos]

The following may be of some help:

Configuring FreeDOS to Access a Samba Share - SambaWiki

wiki.samba.org

and also the following auxiliary parameters for Services->SMB:
https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#LANMANAUTH
https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#SERVERMINPROTOCOL

The DOS client probably also doesn't speak SMB1 (NT1) and so you'll need to drop "server min protocol" lower through an aux parameter.

Do note that you're downgrading your SMB server's security in order to do this. It's an unsupported configuration and so you may hit roadblocks with how our middleware generates samba's passdb.tdb file. I don't see the "lanman auth" parameter immediately on the chopping block for the upstream Samba project, but MS-DOS support will definitely be removed when SMB1 support is removed in a future release of upstream Samba.

 

[anodos]

There have been some enthusiasts who have gotten a Trash-80 to speak SMB3 through an ESP32 microcontroller and libsmb2. https://github.com/apuder/TRS-IO https://github.com/sahlberg/libsmb2 So theoretically there is some ability to make legacy hardware use modern SMB protocols. Might be a fun hobby project for old hardware.

 

[BjörnWagner]

Hi,

IT WORKS Thanks a lot.

I had to change the min protocol to CORE, thx anodos,
and adjust the authentication, thx swissroot.

I would never have figured out the trick with the lanmanager hash.

My parameter setting for the SMB service is :

lanman auth = Yes
client ntlmv2 auth = no
client plaintext auth = Yes
server signing = disabled
server min protocol = CORE

You saved me form being a Floppy-DJ ;-)

Best regards,
Björn

 

[anodos]

Samba 4.13 Features added/changed - SambaWiki

wiki.samba.org

Code:

 Parameter Name                     Description                Default
 --------------                     -----------                -------
 ldap ssl ads                       removed
 smb2 disable lock sequence checking                No
 domain logons                      Deprecated                 no
 raw NTLMv2 auth                    Deprecated                 no
 client plaintext auth              Deprecated                 no
 client NTLMv2 auth                 Deprecated                 yes
 client lanman auth                 Deprecated                 no
 client use spnego                  Deprecated                 yes
 server schannel                    To be removed in 4.13.0
 server require schannel:COMPUTER   Added

So "client ntlmv2 auth" is on the chopping block for samba 4.14. TrueNAS 12.1 (freebsd) and TrueNAS SCALE are on Samba 4.13. You may want to verify that the _client_ parameter is really needed.