China DOS Union

A DOS system can connect to Windows 95/NT/XP by installing "Microsoft Network Client 3.0".
To establish a connection, first download the following files from Microsoft's FTP server:
ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe
ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-2.exe
(these two files can also be found in \clients\msclient on the NT4 Server installation CD)
The above two are self-extracting files. Copy all extracted files onto two floppy disks, named DISK1 and DISK2 respectively, unless you want to install the TCP/IP protocol, or want to use the network under Windows 3.1, in which case only DISK1 is needed).
The installation files above do not include drivers for newer network cards, so next let's update them manually. That way your network card model will appear in the installer's selection list.
First, find the NDIS2 for DOS driver directory on your network card driver disk. There should be a file named OEMSETUP.INF in it. Copy the contents of the section in OEMSETUP.INF (just one line) to the same place in WCNET.INF on DISK1. Then copy the former's section and section as-is to the end of the latter, and make appropriate modifications by following the similar sections in the latter. Then copy the DOS driver from the network card driver disk to disk 1. At this point the MS Network Client installation disk has been successfully updated, and you will be able to select your network card model during the later installation process.
Now start installing MS Network Client. Run SETUP.EXE on DISK1, and the welcome screen will appear. Press Enter for the next step, then choose the installation directory; the default is fine. Next choose the network card type and select the one that matches your card. The next step is setting the Network Buffer; press Enter to confirm. The system will then prompt you to create a user name (User Name). After entering and confirming it, the installation summary screen will appear. Choose Change Names and enter an appropriate computer name (Computer Name) and workgroup name (Workgroup Name). If you want to log on to an NT domain, you also need to enter the domain name (Domain Name). After confirming everything is correct, press Enter.
Choose "Setup Options". If you are not logging on to a domain, for the Redir item you only need to select Basic-Redirector to save memory. If you want to log on to a domain, you must set "Logon Validation" to "Logon to Domain", and Redir Option will also be set to Full Redirector" at the same time.
Then choose "Change Network Configuration". In its sub-item "Change Setting", select the proper port address and IRQ for your network card. In the "Add Protocol" item, add network protocols; you can also choose "Remove" to delete some unnecessary protocol to save memory. If you added the TCP/IP protocol, you also need to configure it manually (IP, gateway, etc., similar to WIN, not described in detail here). Note that in MS Network Client, different sections of the IP address are separated by spaces, not dots. After all settings are finished, choose Network configuration is correct and press Enter to confirm. The installer will start copying files. After file copying is complete, confirm and the system will reboot automatically. At this point, Microsoft Network Client installation is complete.
After the system restarts, enter the user name and password to log on to the network. At this time Microsoft Network Client can still only be used fully as a client, and can only access shared resources on other machines. If you want to provide shared resources to other network users under DOS, first go to MS's FTP and download the following file:
ftp://ftp.microsoft.com/softlib/mslfiles/wg1049.exe
Copy the four extracted files (NET.EXE NET.MSG............) into the directory where Microsoft Network Client is located, overwriting the original files. Modify the SYSTEM.INI file under it, set both filesharing and printsharing to yes, and then you can use the net share command to provide file and print services to other computers. Before that, you must load share.exe and start the server service. If you do not want to be prompted every time, you can also add them to autoexec.bat:
Lh share
Net start server

End of full text.

Is it original? Not bad!

Hehe. This article. Purely original. If there are similarities? Impossible!

I now have all the new and old computers in the company connected through a switch. After installing msclient3.0, the DOS machine can access shared files on the XP and win200 machines, and copying in and out both works; the XP and win200 machines can only see the DOS machine in Network Neighborhood, but cannot access files on the DOS machine. If any expert can help me get this sorted out, I'll give him a gift.

Double-clicking the DOS computer name directly in Network Neighborhood doesn't seem to work too well, but you can use net use to map the DOS machine's shared resources as a network drive for access.
For example, if the DOS machine name is user1 and the shared directory name is share1, you can execute the command:
net use z: \\user1\share1, then drive z: will access the shared resources on the DOS machine.

[ Last edited by Michael on 2005-11-6 at 20:46 ]

Thanks to Michael. After mapping it as a network drive, an extra Z drive appeared in Explorer. I can copy files out, but I can't copy files into it. It's the same when executing the copy command at the command prompt. Is there any way to solve this?
One more question: which file automatically saves the commands executed in the XP and win2000 command prompt, so that if the system is reinstalled one day, I can just copy that file and won't have to execute so many commands again?

Originally posted by sxsjp at 2005-11-8 14:56:
Thanks to Michael. After mapping it as a network drive, an extra Z drive appeared in Explorer. I can copy files out, but I can't copy files into it. It's the same when executing the copy command at the command prompt. Is there any way to solve this? ...

The mapped drive is actually a folder on the other machine. Most likely that folder is set to read-only and doesn't have write permission, so no files can be copied into it.

Thanks for JonePeng's reply
The mapped drive was just created on DOS with md, so it can't possibly be a read-only folder.
I originally had this problem too when sharing the XP machine on the DOS machine. Later, after executing net user on XP, I could copy files in and out. But now executing net user on the DOS machine doesn't work. I don't know which command I need to run?

[ Last edited by sxsjp on 2005-11-9 at 13:58 ]

Thanks OP, but I can't download the tool in the article.
Thu Nov 10 16:53:23 2005 LIST /softlib/mslfiles/wg1049.exe
Thu Nov 10 16:53:36 2005 425 Can't open data connection.
Could you send me one too. marcoak@gmail.com

Re marcoak:
It should be a problem with your ftp client settings. I can download it normally here.

But I uploaded a copy for you.

I couldn't download it even with IE myself. Thanks to the OP, I downloaded the attachment.

The attachment can't be extracted!
It's not right!
WHY？

OP, could you send me the three programs mentioned in your article?
ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe
ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-2.exe
ftp://ftp.microsoft.com/softlib/mslfiles/wg1049.exe
I can't download a single one, and the attachment you uploaded later also has extraction problems!
My email is:wxj7749@yahoo.com.cn
Thanks!

re efeng2008:

I just downloaded the attachment I uploaded again, and there is absolutely no problem.
Also, I don't have these three files on hand either.
And these three links have not expired.