Win2000 terminal problems and solutions

             After installing and setting up according to the relevant content of this site, Windows 2000 terminal can be started, but some faults may be encountered during the installation process. This article will analyze various faults and propose solutions. In addition, there are still some problems in the terminal technology in practical applications, such as the installation of application software, the addition of Chinese character input method, server security problem, multi-user automatic login and DOS program compatibility, etc. This paper proposes a reasonable solution to the above problems.
1. Common faults and handling
(1) Fault 1: When installing Windows 2000 Server, the system prompts "Invalid NetBIOS name" <2> Fault 2: When the server upgrades domain, install Active Directory (Active Directory) failed, the system prompts: Can not access the network location ...
(3) Fault 3: After the installation of the W2KRPL (Windows 2000 RPL patch), the system restarts, the system prompts to find a Error, when starting the remote management program, the prompt "Do not start the remote boot service", when manually starting the remote boot service in the management tool's "service", the system prompts: error 998, memory allocation is invalid.
(4) Fault IV: When creating a new profile, configure the boot record is not found in the drop-down list of DOS (attention before adding NIC)

(5) Failure Friday: install MetaFrame 1.8 a system prompts the following error message: MateFrame is designed to work on windows 2000 (Network operting System Version 5.0)
(6) Fault 6: The terminal displays a blue screen error such as COM PORT when connecting to the server under DOS, but knocks After you press Enter, you can log in to the server for normal use. You cannot use the mouse after entering.
(7) Fault 7: When connecting to the server under IPX protocol under DOS, the following error message appears:
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 with 256 colors 800x600, the ICA boot screen will crash and it will connect normally when it is 16 colors 640x480.
(9) Fault 9: After installing wfw311, the diskless DOS workstation cannot be started, and it will appear until
NET START RDR /RPL:YES /FIT:YES /COMPUTERNAME:(COMPUTER_NAME) /HIMEM:YES The following tips: General failure writing drive cAbort, Retry, Fail?
Fault 10: After installing Windos32, the mouse can not be used, but in the DOS state can be driven normally, and can be used under the application.
(10) Fault 11: After entering WIN2000 on the workstation, the mouse will wait for about 30 seconds to work.
(11) Fault 12: The terminal client logs in to the server as a normal user account, and appears when logging in. The local policy of this system does not allow you to use the interactive login " warning box, "OK", then return to the original operating system and cannot connect to the server.
2, application software installation and use problems
Windows 2000 terminal system installation is successful, you also need to set the relevant application software environment, and the diskless network is the terminal all application software is installed on the server side settings After successfully installing a piece of software on the server, all terminals can use the same software as on the server. Everyone knows that installing software under Windows 98 or Windows NT 4.0 can be done easily by simply "Setup". If the software installation file "Setup.exe" is run directly on the Windows 2000 server, the system often displays an error message saying "The terminal server failed to install", and the installation cannot continue. Therefore, when installing software on a terminal server, you must first put the server in the installation state, but then install it, so that the software installation can continue normally. This means that the application software can be installed as in Windows 9x before adding Terminal Services. After adding Terminal Services, it cannot be installed this way. However, it is impossible to install all the applications in advance (for example, adding new software, application software upgrades, etc.) In general, the software installation after the terminal service is added can be performed as follows: double-click the "My Computer" icon Go to the "My Computer" screen, double-click the "Control Panel" icon, go to the "Control Panel" screen, find the "Add/Remove Programs" icon, double-click it, and go to the "CD or floppy disk " button. The "from the floppy or CD-ROM installer interface", click "Next" appears "Run installer" interface, enter the path and file name of the installation file in the "Open" text box, single Click the "Next" button, and then the installation wizard interface of the software appears. Next, just like the regular installation method, you can complete the software installation according to the installation wizard prompt, most software, such as: Photoshop6.0 , AutoCAD2000 WPS2000, NetAnts, and Orient Express 2000 can complete the installation of the terminal server through this installation method. Office2000, etc. must be installed in a special way.
(1) Installation of terminal input method
Windows 2000 Server comes with input methods such as full spell, Zheng code and smart ABC. If you need to add third-party input method, the following is a five-character font description (note that Many of the five-stroke input methods under Windows 9x are not normal under Windows 2000. It is recommended to use the Wang code five-stroke input method in the office 2000 installation CD version 86)
(2) Problems with the use of software
Large Most software can be used normally on the terminal client after installation on the terminal server, and some software, such as OICQ, CUTFTP, Kingsoft typing wizard, etc., need to save some user information, use information, etc., and this information is It is stored in the folder where the application software is located, so we need the terminal user to have write access to the folder, so that it can be used normally on the terminal client.
3, security issues and solutions
Server security issues, should be the network's primary problem. If the terminal client can arbitrarily delete the server's files and modify some important settings, then even if the network speed is fast, the application software is rich, and it cannot be said that the network is a practical network. For the convenience of description, when logging in to the client, the administrator is logged in as the administrator. The security of the setup is extremely poor. The server can delete the server file or even shut down the server. In practical applications, a terminal working group can be established under normal circumstances, and an end user account is established for it. This section will explain the local login, directory security permissions, and group policy settings with an example. Assume that the terminal working group is yxz and the terminal users are T01, T02, T03...
Copyright © Windows knowledge All Rights Reserved