You need the MS Client 3.0 software in order to use NET commands from within FreeDOS. (https://www.lazybrowndog.net/freedos/virtualbox/?page_id=575).

Alternatively, you can use something like EtherDFS to share folders over raw Ethernet frames (https://etherdfs.sourceforge.net/). FreeDOS has an installable package for EtherDFS, you just need to set up the server on the other side.

There is a client for VB Shared Folders for DOS : https://git.javispedro.com/cgit/vbados.git/about/
(Shameless plug...)

If you don't actually need a shared folder, and just want to copy files back and forth over
a network, my DDLINK is probababy the easiest way to do it. You run DOSBOX with virtual
NE2000 on the host .. you will need an NE2000 "packet driver" (NE2000.COM) as well as
one for VirtualBox AMD PC-Net (PCNTPK.COM)

Then you just run DDLINK both in DOSBOX and on the DOS booted on VM
and you can copy files back and forth. You don't have to "install" anything
on either end!

I do this all the time with VirtualBox as well as actual DOS booted under DOSBOX.
See DBDOS.ZIP in downloads on my site - it has all the software you need:
-- DDLINK.COM, NE2000.COM and PCNTPK.COM

ifrit05 wrote on 2025-03-30, 18:04:

You need the MS Client 3.0 software in order to use NET commands from within FreeDOS. (https://www.lazybrowndog.net/freedos/virtualbox/?page_id=575).

Alternatively, you can use something like EtherDFS to share folders over raw Ethernet frames (https://etherdfs.sourceforge.net/). FreeDOS has an installable package for EtherDFS, you just need to set up the server on the other side.

Thanks I'll take a look at that.

DaveDDS wrote on 2025-03-30, 21:59:

If you don't actually need a shared folder, and just want to copy files back and forth over a network, my DDLINK is probababy th […]
Show full quote

If you don't actually need a shared folder, and just want to copy files back and forth over
a network, my DDLINK is probababy the easiest way to do it. You run DOSBOX with virtual
NE2000 on the host .. you will need an NE2000 "packet driver" (NE2000.COM) as well as
one for VirtualBox AMD PC-Net (PCNTPK.COM)

Then you just run DDLINK both in DOSBOX and on the DOS booted on VM
and you can copy files back and forth. You don't have to "install" anything
on either end!

I do this all the time with VirtualBox as well as actual DOS booted under DOSBOX.
See DBDOS.ZIP in downloads on my site - it has all the software you need:
-- DDLINK.COM, NE2000.COM and PCNTPK.COM

Thanks Dave. However, I prefer to use FreeDOS because my intent is, at some point, run malicious software there and I'm not sure how much DOSBox can protect my system.

javispedro1 wrote on 2025-03-30, 21:30:

There is a client for VB Shared Folders for DOS : https://git.javispedro.com/cgit/vbados.git/about/
(Shameless plug...)

Thanks Javi! I'll try this since it seems to be the best solution for me.
I'll get back here when I try it.

I just want to share with everybody that Javis' shared folder driver worked!
It was very easy to make it run and I even added an entry into FDAUTO.BAT to install the driver when the system boot.

Thank you all for the help!

DrH wrote on 2025-03-31, 13:27:

Thanks Dave. However, I prefer to use FreeDOS because my intent is, at some point, run malicious software there and I'm not sure how much DOSBox can protect my system.

I don't know why you couldn't - packet drivers and DDLINK work well within FreeDos.
(I fact, one of the boot disk images I include in DBDOS is a version of FreeDOS!)

And I wasn't suggesting you use DosBox (in fact if will let DOS malware access any directory on the host that
you have MOUNTed) - I mentioned it because I recently produced DBDOS which boots actual DOS boot floppies
with DosBox (which would run as safely any other virtual machine).

When run in this way the booted DOS can't directly access the HOST file system.
Which is why I've included all the things you need to access via a network.

And if you are planning to test malware - DDLINK might be a good choice as it uses raw
network packets (not TCP, IPX, SMR etc.) and those protocols don't even have to be installed!
- so any malware wanting to write things on your network would have to know about DDLINK
and it's protocol - yes, the protocol is documented (by me)... but DDLINK is not well known/common
enough that it would be worth it for malware ... and it's a file transfer protocol that I "invented"
and as far as I know - no other software uses it!

I see your point Dave. Thank you for the suggestions.