China DOS Union

1. You can share resources with the NET USE command, but after opening the graphical interface with the NET command, you can't find Network Neighborhood.

As for this problem, I haven't found a solution either. Hopefully a brother who knows can come up and explain it.

2. When using the NET VIEW command, it reports Error 6118: The list of servers for this workgroup is not currently available.

This problem has a lot to do with the network environment. When I was testing, sometimes it would report this error, and sometimes it wouldn't. Sometimes the command would fail just now, but repeating it once would make it work.

. When using the NET VIEW command under DOS to view the workgroup, it's recommended to first check the workgroup on a 2K/XP machine and test whether you can normally view the member list of the workgroup. If

it doesn't work there, then don't try it under DOS yet. First find the cause, make sure the workgroup list can be viewed normally under 2K/XP, then switch to the DOS system.

Suggestion: During testing, turn off the power of the switch (or hub), then turn it back on. After a while, boot into DOS, wait a bit after startup finishes, then run the NET

VIEW command for testing.

The 6118 error is shown in the picture:

3. When using the NET USE command, it reports Error 53: The network path was not found.

First use the NET VIEW command to check whether you can see Network Neighborhood. If you can't find Network Neighborhood, then in general the NET USE command will not succeed.

You must pay attention to the usage of the NET USE command: [ NET USE drive_letter: network_host_name\shared_folder_name ]

Example: NET USE E: \\WWW-ZMM7YQYM7L9\TDDOWNLOAD

In the example above, E: is a local drive letter. Note that it must be an unused local drive letter [can be any one]. If there is already an E: drive locally, then you can't use E:. \\WWW-ZMM7YQYM7L9\TDDOWNLOAD is the target net

work path to be shared. WWW-ZMM7YQYM7L9 is the network host name, and TDDOWNLOAD is the shared folder name. The \\ before WWW-ZMM7YQYM7L9 must be written, don't leave it out.

4. When using the NET USE command, it reports Access denied .

This is because you do not have permission to use the network resource. This is a permissions problem, and it shows that you have basically succeeded.

Solution: When logging onto the network, enter a username and password with the corresponding permissions, then you can access the network resources normally.

Example: The shared folder \\WWW-ZMM7YQYM7L9\TDDOWNLOAD can only be accessed by the administrator Administrator, and the administrator password is 1. Then when logging onto the network, the username is

Administrator , and the password is 1 .


5. After installing MS CLIENT 3.0, startup reports insufficient memory.

This is a DOS system configuration problem. You need to load extended memory support; just configure the CONFIG.SYS file.
Add one line to the CONFIG.SYS file: DEVICE=\DOS\HIMEM.SYS . Note that \DOS is the location of the HIMEM.SYS file, so configure it according to your own situation.

Insufficient memory is shown in the picture:

The CONFIG.SYS file configuration is shown in the picture:

6. Points to note when configuring the TCP/IP protocol

If you want to configure the IP address manually, there is one thing you must pay attention to: the value of Disable Automatic Configuration must be 1. If this item is 0, the IP configuration that follows will be invalid.

As shown in the picture:

A few tips:

When installing MS CLIENT 3.0 in a VMWARE virtual machine, it's recommended to copy the installation files onto the hard disk and create a separate folder for them, so the installation is much simpler.

As shown in the picture:

The installation files for MS CLIENT 3.0 are placed in the DOSNET folder on drive C:, with two folders, DSK3-1 and DSK3-2. DSK3-2 is the installation package for the TCP/IP protocol. The IBMDOS folder on drive C: contains the DOS network card driver for the VMWARE virtual machine.

The screen after copying MS CLIENT 3.0 to the hard drive:

When installing MS CLIENT 3.0, if you select the TCP/IP protocol, at the end it will ask you to specify the folder where the TCP/IP protocol package is located, as shown in the picture:

Well written. The thing I made is even more convenient and simpler. It also has all kinds of setting options for MS CLIENT 3.0.
And it supports multiple identical network cards on the motherboard.

http://netbootdisk.com/forums/viewtopic.php?t=605

http://www.cn-dos.net/forum/viewthread.php?tid=19003&fpage=2

, looks like an outsider after all

Bump!

Very nice