Configuring FreeDOS to Access a Samba Share
From SambaWiki
Introduction
This documentation describes how to access Samba shares from FreeDOS using the MS Client 3.0
.
DOS is not an official supported OS by Samba. |
Installing FreeDOS
- Download the latest version of the FreeDOS installer CD from http://www.freedos.org/download/
- Install FreeDOS on your hard drive.
- Select the
user defined
mode. - Select the following program packages to install:
- base
- net
- Select the
Downloading the Network Interface Card Driver and MS Client
- Download the DOS version of your network interface card (NIC) driver.
- If you run FreeDOS in a VM, use the following NIC models and NDIS2 drivers for DOS:
Hypervisor NIC Model Driver KVM RTL8139 http://www.realtek.com.tw Select: Downloads
/Communications Network ICs
/Network Interface Controllers
/10/100M Fast Ethernet
/PCI
/Software
. Download:NDIS2 driver for DOS
VirtualBox PCNET http://support.amd.com/en-us/search/utilities Download: NDIS2 driver for Windows 3.1
- If necessary, extract the downloaded driver archive on a Windows or Linux machine.
- Download the two
MS Client 3.0
installation disks from:
- For an easy transfer to the FreeDOS client, create a CD with the NIC driver and the
MS Client
.
Installation and Configuration
- Start FreeDOS and insert the CD with the Network Interface Card (NIC) driver and
MS Client
.
- Create a temporary directory:
> mkdir C:\TEMP\
- Create temporary directories for the
MS Client
disks:
> mkdir C:\TEMP\DISK1\ > mkdir C:\TEMP\DISK2\
- Unpack the
MS Client
into theDISK*
folders. For example, ifD:
is your CD drive:
> cd C:\TEMP\DISK1\ > D:\DSK3-1.EXE > cd C:\TEMP\DISK2\ > D:\DSK3-2.EXE
- Create a temporary directory for the NIC driver and copy the files from the CD. For example:
> mkdir C:\TEMP\NIC\ > copy D:\DRIVER\*.* C:\TEMP\NIC\
- Install
MS Client
:
- Start
SETUP.EXE
:
- Start
> cd C:\TEMP\DISK1\ > setup.exe
- Select
*Network Adapter not shown on list below
and enter the path to your NIC driver. For example:C:\TEMP\NIC\
- Select
- Select the following environment settings:
- Names: Adjust the settings to your environment.
- Setup options:
- Redir Options:
Basic redirector
- Startup options:
Do not run network client
- Logon validation:
Do Not Logon to domain
- Redir Options:
- Network configuration:
- Remove the
NWLink IPX Compatible Transport
protocol - Add the
Microsoft TCP/IP
protocol
- Remove the
- Add protocol
Microsoft NetBEUI
- After you saved the options, the setup asks for the driver disk. Enter the path to the second disk. For example:
C:\TEMP\DISK2\
- Reboot your computer.
- After the reboot, the following error is displayed:
MS-DOS LAN Manager v2.1 Netbind Error: 7906 Unable to open PROTMAN$ NET0111: Error accessing NEMM.DOS TCP 1.0 not loaded. NET0111: Error accessing NEMM.DOS. Tiny RFC 1.0 not loaded. Press any key to continue NET0111: Error accessing NEMM.DOS. NMTSR 10 not loaded. Press any key to continue Error 3658: IFSHLP.SYS driver is not installed.
- The error is caused by different configuration files used in FreeDOS and MS-DOS. The
MS Client
setup added the drivers to theCONFIG.SYS
MS-DOS file. However FreeDOS uses theFDCONFIG.SYS
. To fix:
- Start the
edit
tool and open theC:\FDCONFIG.SYS
file. - Replace the content of the file with the follwing commands:
- Start the
SET DOSDIR=C:\FDOS LASTDRIVE=Z BUFFERS=20 FILES=40 DOS=HIGH DOS=UMB DOSDATA=UMB DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG DEVICEHIGH=C:\NET\IFSHLP.SYS SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT
- Save the changes and close the file.
- Edit the
AUTOEXEC.BAT
file:
- Start the
edit
tool and open theC:\AUTOEXEC.BAT
file. - Replace the content of the file with the follwing commands:
- Start the
@ECHO OFF SET PATH=C:\NET;%DOSDIR%\BIN SET NLSPATH=%DOSDIR%\NLS SET TEMP=%DOSDIR%\TEMP SET TMP=%TEMP% LH FDAPM APMDOS LH DOSLFN DEVLOAD /H /Q %DOSDIR%\BIN\UIDE.SYS /H /D:FDCD0001 /S5 SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D /D:?FDCD0002,D /D:?FDCD0003,D SET AUTOFILE=%0 SET CFGFILE=C:\FDCONFIG.SYS
- To initialize the network at startup, append the following commands:
LH C:\NET\NET.EXE INITIALIZE C:\NET\NETBIND.COM LH C:\NET\UMB.COM LH C:\NET\TCPTSR.EXE LH C:\NET\TINYRFC.EXE LH C:\NET\NMTSR.EXE C:\NET\EMSBFR.EXE
- Save the changes and close the file.
- If you are using dynamic IP settings, skip the following step:
- To configure a static IP:
- Start the
edit
tool and open theC:\NET\PROTOCOL.INI
file. - Update the following settings to use a static IP:
- Start the
[TCPIP] ... DefaultGateway0=0 0 0 0 SubNetMask0=255 0 0 0 IPAddress0=0 0 0 0 DisableDHCP=1 ...
The IP addresses and network mask options use spaces instead of a dot as octet separator. |
- Save the changes and close the file.
- Reboot your client.
- Ping an IP address in your network to verify the network connection.
- To list computers in your network:
> net view
- To mount a share from a server, run:
> net use X: \\SERVER\SHARENAME