DOS ain't dead - no access to current Samba

pixel24

09.06.2020, 15:47

no access to current Samba (Users)

Hi@all,

a friendly "hello"... I'm new here.

I have installed FreeDos 1.2 as a VM in Virtualbox. I have set up the network connection according to these instructions:

https://www.lazybrowndog.net/freedos/virtualbox/?page_id=575

Username, Workgroup and Domain I have adapted accordingly.

TCP/IP works. Server is accessible under IP and hostname. However, access to shares does not work.

net view
net use x: \\[IP odr name]\share

Error message: "Network Resurchse is not available". The server is a Linux / Samba 4.10

SMBv1 and NTLMv1 are disabled by default. But I have activated them for testing which does not work either.

Has anyone managed to access a Samba share (current version) from FreeDOS?

best regards
pixel24

glennmcc

North Jackson, Ohio (USA),
24.06.2020, 18:52

@ pixel24

no access to current Samba

Post reply

> TCP/IP works. Server is accessible under IP and hostname. However, access
> to shares does not work.
>
> net view
> net use x:\\[IP odr name]\share
>
> Error message: "Network Resurchse is not available". The server is a Linux
> / Samba 4.10
>
> SMBv1 and NTLMv1 are disabled by default. But I have activated them for
> testing which does not work either.

Just grasping at straws here but, might try forward slashes instead of backslashes ?

x://[IP odr name]/share

---
--
http://glennmcc.org/

pixel24

30.06.2020, 12:26

@ glennmcc

no access to current Samba

Post reply

I've already tried too much around and therefore reinstalled. I have installed FreeDOS in VirtualBox according to these instructions:

https://itsfoss.com/install-freedos/

After the network setup I have a working TCP/IP.

If I understand everything correctly, I now need the MS-Client 3.0.

What I don't understand is that I still need a network card driver for the installation/configuration of the MS-Client. No matter which manual:

https://www.lazybrowndog.net/freedos/virtualbox/?page_id=575

or

https://wiki.samba.org/index.php/Configuring_FreeDOS_to_Access_a_Samba_Share

TCP/IP is already working in my FreeDOS VM. Why do I still need the "NDIS2 driver for Windows 3.1"?

Which driver do I need to install to make FreeDOS work in VirtualBox?

andrewbird

Cornwall, UK,
30.06.2020, 20:10

@ pixel24

no access to current Samba

Post reply

> After the network setup I have a working TCP/IP.

Yes, but since there was no single standard on DOS for TCP/IP quite often only the tools that came with the TCP/IP software will be able to use it.

> What I don't understand is that I still need a network card driver for the
> installation/configuration of the MS-Client.

Well because of the above, MS-Client wants to install its own network stack. I tried this myself a while ago and used the supplied ne2000 driver that came with MS-Client rather than NDIS.

Regarding MS-CLient working with the latest version of Samba I'm not sure that's still possible due to Samba's dislike of older encryption standards. I did have it working with a not quite current version. I no longer have my kvm guest that I tried my dosemu2/msdos6.22/ne2000/msclient3 against, so I can't be entirely sure what version it was, I suspect the Samba version I used was that from Ubuntu 18.04 as shipped, not upgraded.

Hope it helps, Andrew