VOGONS


First post, by rwGast

User metadata
Rank Newbie
Rank
Newbie

First of all I'm sorry if this is the wrong board to post on, wasn't really sure.

I am running a samba share on a raspberry pi, network name RasPi5. I am able to access it from all my other windows/linux boxes. It is an open share no PW needed. I read through this post
Working configuration for Win98 / Linux Samba share, and tried following all the instructions with no luck.

Im not sure what how to install/enable lanman. On the windows side I am using the same log in and password as my linux account, I turned on file sharing and have installed active directory update. I also edited the registry, following the other threads instructions.

The attachment aa20260727_182003.jpg is no longer available

This is the share part of my smb.conf on the pi

[NetStore]
comment= Network Shared Folder by Samba Server on Ubuntu
path = /mnt/netshare
force user = smbuser
force group = smbgroup
create mask = 0777
force create mode = 0777
directory mask = 0777
force directory mode = 0777
public = yes
read only = no

workgroup = WORKGROUP
netbios name = Raspi5
client ntlm auth = yes
client ntlmv2 auth = No
ntlm auth = yes
restrict anonymous = 1
server min protocol = NT1
lanman auth = no
client lanman auth = no
unix extensions = no

any ideas?

Reply 1 of 1, by DaveDDS

User metadata
Rank Oldbie
Rank
Oldbie

I have no idea if this will help - perhaps there's some nugget of information you can use here ... Way back in the day I made these notes about setting up access to a Winblows (SMB) network from DOS:
-----------------------------------

Microsoft has the Lan Manager client for DOS, which provides access to
MS networks. I don't know if it is still available as a product, however
I found it in the CLIENTS directory of the WinNT4 server evaluation disk
that came with Microsofts "Internet Information Server" evaluation kit.

There is another DOS client called "The Workgroup Connection". I found
it in the software library samples of an older (Dec95) MS TechNet CD.

If you have Windows For Workgroups, you already have everything you need
to access an MS network from DOS. If you already have WFW setup on the
machine (and plan to leave it there), you don't have to do anything...
Just use the NET command to activate the DOS network client outside of
windows.

If you want to use the DOS client without having the rest of windows
hanging around, you can distill it down to a minimum set of files.
Note that is provides a client only... you have to run WFW to share
resources on your machine:

WFW files needed to access network from DOS:
NET.EXE
NET.MSG
NETH.MSG
IFSHLP.SYS
NDISHLP.SYS
PROTMAN.DOS
PROTMAN.EXE
WFWSYS.CFG
SYSTEM.INI
PROTOCOL.INI

You also need the real mode driver for your network card, which will
be listed in the netcard= entry of the [network.drivers] section of
SYSTEM.INI. In my case, I use NE2000 compatibles, and SMC/WD 8013's,
which use one of the following:
NE2000.DOS - NE2000 Compatible
SMCMAC.DOS - SMC/WD 8013

If you want to trim SYSTEM.INI, you need only the following sections:
[Network]
[network drivers]
[Password Lists]

Make sure the devdir= entry under [network drivers], and all
of the entries under [Password Lists] point to the directory
where you have setup these files.

You have to load IFSHLP.SYS in CONFIG.SYS at boot time, just
as you do for WFW.

Once setup, you can use the NET command to start the network,
make connections etc. Use /? for help: NET /? | MORE

https://dunfield.themindfactory.com ; "Daves Old Computers" ; SW dev addict best known:
ImageDisk: rd/wr ANY floppy PChw can ; Micro-C: compiler for DOS+ManySmallCPU ; DDLINK: simple/small filecopy(w/o netSW)via Lan/Lpt/Com