The DOS SMB1.0 stack is period software, but that, plus the nic driver, will consume every scrap of your upper memory and then some.

You are better off using modern stuff, like mbrutman's mtcp.

https://www.brutman.com/mTCP/

That gets the job done, without breaking the bank.

It only needs a packet driver, which are *substantially* smaller than ndis2 drivers. Packet drivers should be on the same dos driver diskette as an ndis2 driver, usually for use with novell's odi model. You dont need anything more than this packet driver to use netdrive.

But, if you insist on the path of pain and perdition...

You will need:

DOS NDIS2 driver diskette for your NIC.
Microsoft Lan Manager for DOS disk set.
greater than 128kb of free upper memory.
enable SMB1.0 features on your windows box / network share
thick skin

(I'd provide links, but the ndis2 drivers are nic specific, and the lan manager for dos set is still under copyright, and maybe not proper to link to here.)

You can look into Brutman's netdrive as well. Works great on my PCjr, 8086, 386, etc. systems. Requires mTCP as well to work

Here's one of Brutman's YouTube videos about it
https://www.youtube.com/watch?v=86QSxJO8otI&t=3s

Period correct would be the "Microsoft Network Client 3.0" which can be found as stand alone package or on NT Sever CD in the \CLIENTS\MSCLIENT folder
https://youtu.be/_eOImLHa-Tw?si=-nLHa0uawYPNwaBN

or
Microsoft LAN Manager 2.2c
https://youtu.be/oqMzF41dyvk?si=NQABF5xphYb-jMhD

or my personal choice Windows for Workgroups

all 3 do use a lot of memory, however no need to load the drivers if your not going to use the network, I have a "net.bat" file I run if and when I need the network which is less then half the time.
SMB is slow but convenient as it's built into windows. XP plays nice with these old clients as long as you set up your network in a way XP can understand. That is make sure everyone is in the same workgroup and makes life much easier if you use the same username/password across all computers. (Password is recommended, even if its only 1 character as sometimes windows gets confused with a blank password)

FTP is another period correct option but not built into windows, you would need to run a ftp server such as mtcp above. FTP is quicker and easier to get working with different generations of OS's but personally don't find it as convenient as SMB.

If you want to transfer files over the network, the absolutely easiest and IMO convenient thing is to use FTP server on your vintage systems. Then just connect to this server with a client from your modern system. It is simple and you don’t need to make any changes to your modern systems or resources. And you get to use modern FTP clients with drag and drop UIs and whatnot.

I have this kind of setup for every of my DOS systems and most othe win9x boxes. I can’t live without DOS networking and floppy hassle is something that I definitely don’t miss from the past.