Win2K terminal Problems and Solutions

After installing and setting according to the content of this site, you can start the Windows 2000 Terminal. However, some faults may occur during the installation process. This article will analyze various faults and propose solutions. In addition, there are still some problems in Terminal Technology in practical applications, such as installation of application software, addition of Chinese Character Input Methods, server security issues, multi-user automatic logon, and DOS program compatibility, this article provides a reasonable solution to the above problems.

1. Common Faults and troubleshooting

(1) fault 1: When installing Windows 2000 Server, the system prompts "invalid NetBIOS name"

(2) fault 2: when the server upgrades the domain, the installation of Active Directory (Active Directory) Fails. The system prompts: The network location cannot be accessed ......

(3) fault 3: After installing Ling Xin's W2KRPL (Windows 2000 RPL patch), restart and the system prompts an error, when the remote management program is started, the system prompts "the remote start service is not started". When you manually start the remote start service in the "service" of the management tool, the system prompts: Error 998, the memory allocation is invalid.

(4) fault 4: when creating a configuration file, the DOS boot record cannot be found in the configuration drop-down list (note that it exists before the NIC is added)
(5) fault 5: The System prompts the following error message when installing MetaFrame 1.8a: MateFrame is designed to work on windows 2000 (Network operting System Version 5.0)

(6) fault 6: a blue screen error such as com port occurs when the terminal connects to the server under DOS. However, after you press enter, you can log on to the server and the mouse will not be available.

(7) troubleshooting 7: the following error message is displayed when I connect to the server using IPX protocol in DOS:

Connecting to 'w2k (w2k is the connection name)

Support not available for IPX check you system configureation

(8) fault 8: When the RPL diskless DOS Workstation is connected to the 256-color 800x600, the system crashes after the ICA startup screen appears and can be normally connected when the 16-color 640x480.

(9) troubleshooting 9: After wfw311 is installed, the diskless DOS Workstation cannot be started.

Net start rdr/RPL: YES/FIT: YES/COMPUTERNAME :( COMPUTER_NAME)/HIMEM: YES, the following prompt appears: General failure writing drive cAbort, Retry, Fail?

Fault 10: After ipvs32 is installed, the mouse cannot be used, but the driver can be properly driven in DOS state and used in applications.

(10) fault 11: After Entering WIN2000 on the workstation, the mouse will wait about 30 seconds before it can work.

(11) troubleshooting 12: When a Common User Account of the terminal client logs on to the server, the warning box "the local policy of this system does not allow you to use interactive logon" appears. After "OK, unable to connect to the server after returning to the original operating system.

2. Installation and Use of Application Software

After the Windows 2000 terminal system is successfully installed, you also need to set up the relevant application software environment. Unlike the diskless network, all the application software on the terminal is installed on the server, after a software is successfully installed on the server, all terminals can use the software as on the server. As we all know, installing software on Windows 98 or Windows NT 4.0 requires a simple Setup. If you directly run the Software Installation File "Setup.exe" on a Windows 2000 server, the system will often prompt "Terminal Server Installation failed", causing the installation to fail. Therefore, when installing software on the terminal server, you must first install the server, but then install it. That is to say, if the application software can be installed as in Windows 9x before the terminal service is added, it cannot be installed after the terminal service is added. However, it is impossible to fully install all applications (such as adding new software or upgrading application software) in advance. In general, the installation of software after the terminal service is added can be done as follows: double-click the "my computer" icon to go to the "my computer" page, and double-click the "control panel" icon to go to the "control panel" page, and find the "Add/delete programs" icon, double-click it to go to the "disc or floppy disk" button. The "install program from a floppy disk or CD interface" appears. Click "Next" to display the "run installer" interface. In the "open" text box, enter the path and file name of the Installation File, click "Next", and the installation wizard interface of the software appears. Next, you can complete the installation of the software as long as you follow the instructions in the installation wizard, for example, Photoshop6.0, AutoCAD2000 WPS2000, NetAnts, and Dongfang express 2000 can be installed on the terminal server. Office2000 and so on must be installed in a special method.

(1) Installation of terminal input methods

Windows 2000 Server comes with full spelling, Zheng code, and smart ABC input methods. If you need to add a third-party input method, the following is a description of the Five-stroke style: (note that many of the Five-stroke style input methods under Windows 9x are not normal in Windows 2000. We recommend that you use the 86 version of the Five-stroke style Input Method on the installation disc of office 2000)

(2) software usage Problems

After most software is installed on the terminal server, it can be used normally on the terminal client. Some software, such as OICQ, CUTFTP, and Kingsoft typing genie, need to save some user information, and the information is saved in the folder where the application is located. Therefore, we need end users to have the write permission for this folder, this ensures the normal use of the client.

3. Security Issues and Solutions

Server security issues should be the primary network issues. If the client can delete the server files and modify some important settings, the network speed is faster, the application software is richer, and the network is not a practical network. For ease of description, you can log on to the server as Administrator when logging on to the client. The security settings are extremely poor. You can delete server files or even close the server on the terminal. In practice, you can create a terminal working group and create a terminal user account for it. This section uses an example to describe local logon, directory security permissions, and group policy settings. Assume that the terminal workgroup is yxz, and the terminal users are T01, T02, and T03 ......