中国DOS联盟

Dear experts:

Our company has several old computers, and it's very inconvenient to always use floppy disks to copy data. So I wanted to directly connect them to the company's Windows 2003 Server. Today, I downloaded DOS 7.10, MSCLIENT 3.0 (disk_1.exe, disk_2.exe) from this site. I first tested with one of the machines. I inserted an RTL8139D network card, formatted the hard disk, installed DOS 7.1 on drive C, then installed MSCLIENT 3.0. The network card driver selected was NE2000 compatible. I added the NETBEUI protocol and the TCPIP protocol. After installation, I restarted the computer, and there was a network card error and no response.

So I searched for relevant information on this site, then started with the network card driver. I copied the *.dos, *.nif files under \NDISDOS\ in the floppy disk with the network card configuration to the \MSCLIENT\ installation directory. I copied the content under the section in Oemsetup.inf and the corresponding content to \MSCLIENT\WCNET.INF. I restored the AUTOEXE.BAT and CONFIG.SYS on the hard disk to before installing MSCLIENT. I deleted the C:\NET directory and reinstalled MSCLIENT. After installation, I restarted the computer. This time the network card driver loaded OK, but when loading the TCPIP protocol, it got stuck, something like TCPTSR.EXE or something.

So I restarted the computer, pressed F5 to not execute AUTOEXEC.BAT and CONFIG.SYS, went to the C:\NET\ directory, opened the PROTOCOL.INI file, modified the subnet mask: 255 255 255 0, changed the IP address to: 192 168 0 188 (this IP is not used in the domain yet), and set DISABLEDHCP to 1. I saved and exited and restarted. This time the TCPIP protocol passed, and the user appeared, I pressed enter; password, I pressed enter; save password, (N) I pressed enter; workgroup password, I pressed enter; then the computer got stuck here and couldn't proceed, but it didn't crash. I restarted several times, and it was always stuck at the workgroup password. I have already created the username on the 2003 SERVER, and I have also enabled the GUEST user on the 2003 SERVER. Please give me some pointers on where the problem is. Thank you in advance!

Last edited by vocabulary on 2006-11-29 at 11:07 AM ]

Has your problem been solved? I also encountered such a problem. My problem is that it has been stuck during DHCP initialization. I completely installed it once. Did you install disk-2.exe during the installation? Is there a problem with the system disk we installed? If there is any good way, please let me know, thank you

The problem hasn't been solved yet. When I installed it, because there was no floppy drive, I extracted the two files DISK_1.EXE and DISK_2.EXE into the same directory \NETSETUP\ on the hard disk and then installed it. Some files in DISK_1 and DISK_2 are the same, and the file sizes are also the same. When I extracted them to the \NETSETUP\ directory, I overwrote them. I don't know if there will be any problem. It seems that there are no installation files in DISK_2? If I'm lucky, maybe I can run into Boss Wengier to give us an answer. Urgent! Urgent! Urgent!!!!

Last edited by vocabulary on 2006-11-29 at 11:06 AM ]

The same situation happened to me. Just now I tried again and it worked. But the loaded sockets package seems incorrect. It is estimated that it is still a problem with tcpip. Let's work together to solve it.

My God! There is a problem with the network card, and now the network card is not detected. I'll go out and buy another one to try at noon when having a meal!

I bought a D-Link DEF 530TX 10/100M network card. After installing it, I copied the two files \NDIS2\DLKDEF.DOS and \NDIS2\DLKFETI.NIF from the CD to the \MSCLIENT\ directory, copied the content in from the \NDIS2\OEMSETUP.INF file to the \MSCLENT\WCNET.INF file, emptied all the content in C:\NET, and reinstalled DOS 7.1. Then I reinstalled MSCLIENT 3.0. I only installed two network protocols, NETBEUI and TCPIP. After installation, instead of restarting, I pressed F3 to return to DOS, modified the C:\NET\PROTOCOL.INI file and C:\NET\SYSTEM.INI file (that is, modified the subnet mask, IP, and DisableDHCP), then restarted.

Successfully executed NET START, and got the prompt: You were logged on, but have not been validated by a server, Therefore, you may not have permission to use some network resources. (The meaning should be successfully logged on, but not validated by the server, possibly unable to access network resources.)

Executed NET VIEW and got: ERROR 6118 :The list of servers for this workgroup is not currently available.

When pinging servername, got: Remote name cannot be resolved.

When pinging 192.168.0.1 (the server's IP), got: echo received from 192.168.0.1 with roundtrip < 50 msec

Successfully mapped the shared disk on the server, net use g: \\servername\files1, got: The command completed successfully, but when going to the g:\ disk and executing dir/w, got: Access denied. Up to this point, I personally think it is already very close to the dawn, but where the problem is, it remains to be worked on. Please, experts, give some advice!

I suspect it's still the issue of insufficient permissions on the server - shared folder. I created a new folder in SERVER2003, shared this folder to everyone with full control, and also gave everyone full control in the security options. But after restarting the workstation and remapping this new shared folder, dir still shows Access denied!

Also, do all the statements in the last few lines of autoexec.bat need to be there?
net initialize
netbind.com
umb.com
tcptsr.exe
tinyrfc.exe
nmtsr.exe
emsbfr.exe
net start

If both NETBEUI and TCPIP protocols are loaded at the same time, there isn't enough memory. I can only either load NETBEUI or only load the TCPIP protocol.

I changed to log in to another WIN2000 PROFESSIONAL, established WORKGROUP on WIN2000, logged in in workgroup mode, not in domain mode. As a result, net view smoothly saw the WIN2000 PROFESSIONAL computer, and successfully mapped the shared disk on WIN2000 PROFESSIONAL, and dir on the network disk also saw all the files in the network disk. But why can't I log in to the WIN2003 SERVER?

Ladies and gentlemen, the problem is solved!!!
I found in a book on my bookshelf: In the default case, Windows 2003 Server Active Directory (AD) requires clients to perform SMB packet digital signing to enhance AD security. But WFW and DOS cannot pass digital signing, so it is necessary to set the . Disable the digital signing restriction:
In , find: and disable it, then disable . In this way, DOS workstations can successfully net view \\servername, and can also successfully map and DIR to browse the materials in the network drive.
But remind everyone that if these two restrictions are canceled, the security of 2003 Server will be reduced. Everyone should be mentally prepared! But fortunately, I only open some design materials for a few old computers in a certain department, and only give read permissions.
Finally, I have to say: The sentence "Books are the ladder of human progress" is really great!

Can you help me try to load sockets.exe in your autoexec.bat? The path is c:\net\soskets.exe. Also, you set disdhcp=1, isn't that turning this item off?

sunshine912240:
After loading SOCKETS.EXE, the following appears: SOCKETS0101: The value for keyword HOSTNAME not found in TCPUTILS.INI file by SOCKETS. I think it might be that the HOSTNAME item needs to be added to the C:\NET\TCPUTILS.INI file. I don't know exactly why it needs to be added. What do you want to use SOCKETS.EXE for? Is it to go online?
In addition, I only used the TCPIP protocol, and DisableDHCP is set to 1.

Last edited by vocabulary on 2006-11-30 at 11:26 AM ]

When you installed DOS 7.1, which add-ons and such did you install? I plan to make a communication program between Windows and DOS. I need to load sockets. If only the NetBEUI protocol is loaded and other computers can be mapped, this indicates that the network card driver is okay. The problem is when loading sockets, it can't be added. Yes, where to add the hostname in which file. I tried this here too, but it just prompts "sockets not load". Is it related to the installation of DOS 7.1?

I haven't installed the Addon. Does "sockets not load" have something to do with the DOS 7.1 installation? I really don't know this problem. Let's see if any experts know.