Shoe Wet Wipe,Shoe Wet Tissue,Shoe Wet Ones Hand Wipes,Shoe Wet Ones Wipes DONGYANG COMEXA SANITARY PRODUCTDS LTD.,CO , https://www.comexawipes.com
Step one, first check the virtual drive letter. If you have entered step two. If not, then the network is not configured. In this case, double-click on the "Network" icon in WINDOWS 9X. The icons of other computers cannot be displayed under WINDOWS 9X. Under WINDOWS 3.X, select "DISK" There is no other computer icon under the "Connet NETWORK DRIVE". At this time, go to step 4 item 4 directly.
Step Two: If you can map a network drive but cannot open a shared computer, consider two factors. One is whether the network is correctly connected, and the other is whether the network connection is normal. The former goes to step three to solve. The latter goes into step four to solve.
Step 3. Check the computer's network username (USE NAME) and password (PASSWORD). When entering the WINDOWS 9X desktop there is a window asking for the correct username and password; enter WINDOWS 3. X, Under "ConTROL PANEL", double-click the "NETWORK" icon and enter the correct user name (LOGO NAME) and password (PASSWORD). The correct user name and password are USER MANAGER FOR on WINDOWS NT. In the DOMAINS USER project, after this step is resolved, go to step 4.
Step 4: The network is not connected properly. The following four factors need to be considered.
1. Hub HUB is working properly. The replacement method can be used to determine whether the original HUB has failed. In addition, sometimes some computers cannot be connected to the Internet, and some computers can be connected to the Internet. It is also necessary to consider whether or not the HUB of the part of the computer that cannot be connected to the network has failed. At present, the HUB is generally cheaper, and the faulty machine can be replaced with a new one.
2. Network cable and RJ45 connector problems. Especially RJ45 connectors are prone to failure. The intuitive check method is: Observe whether the network card's light is flashing, lit and irregularly flashing, indicating that it is working normally; it is lit only and does not flash, indicating that there is a problem with the connection. Cut the RJ45 connector and use a special tool to repress a good RJ45 connector. If the light on the network card is off, the network card is faulty and needs to be replaced.
3. Check if the hardware of the network card is damaged. Each type of network card has a driver, and the self-test program in it can check whether the network card hardware is faulty.
4. Check the network configuration for problems. If the WINDOWS 9X environment, then in the "Control Panel", double-click "System" icon, select "Device Management" menu, and then double-click "Network Adapter" item, under which the network adapter item marked with a yellow exclamation mark on the left, then that The network driver does not work (no yellow exclamation mark on the left of the working network adapter item) and needs to be reconfigured. At this point, double-click the network adapter project, under the "General" menu, the "device status" is displayed as "the device does not exist, can not run normally, or no driver is installed", in the "resources" menu, its "resource settings "Interrupt request" (ie, interrupt number) and input/output range (ie, I/O port) are displayed, and other devices that conflict with this interrupt number are displayed under "Collision Device List". If the network driver does not work properly, delete the network adapter and reinstall it. The installation steps are as follows: (1) Double-click on the "Network" icon or "Network Neighborhood" icon under the "Control Panel" → right-click → select "Properties", the "Network" setting window appears. (2) Under the Identification menu, enter the correct computer name and workgroup name. (3) Under the "Configuration" menu, click "Add" button, "Select network component type", select "Customer" and press "Add" button, select network client such as "MICROSOFT network client", click "OK" Button. (4) In the "Configuration" menu, click "Add" button, "Select network component type", select "Adapter" and press "Add" button, select the correct network adapter NE2000 COMPATIBLE under NOVELL/ANTHEM, press "Confirm button. (5) Under the "Configuration" menu, click "Add" button, "Select network component type", select "Protocol" and press "Add" button to select the appropriate network protocol such as MICROSOFT IPX/SPX compatible protocol, ETBEUI Etc. Press the "OK" button. (6) In the "Configuration" menu, select a network driver such as NE2000 COMPATIBLE → click its "Properties" or double-click the network driver, a window appears. Under its "Driver Type", select the "Enhanced Mode (32-bit and 16-bit) NDIS Driver" item. Its "bind" shows the network protocol. Under its "Resources", select the appropriate interrupt number and I/O address range (I/O port) (7) Under the "Configuration" menu, select "Basic Network Logon Mode" as "MICROSOFT Network Client" Finally, press "OK".
If it is WINDOWS 3. For the X environment, click “DRIVERS†under “NETWORK SETUP†and check whether the network adapter (ADAPTER) and protocol (PROTOCOL) are correct. If not, delete the original (REMOVE) network driver. Add the correct network adapter (ADD ADAPTER) and network protocol (ADD PROTOCO). Next, check the interrupt number and I/O port. Click “SETUP†under “DRIVERS†and select the appropriate one. The "INTERRUPT(IRQ)" and the base I/O PORTs are "5" and "00340".
What is appropriate? That is, the interrupt number and the I/O port must be the same as those set on the network card (the driver of the network card can set the interrupt number and I/O port), and it does not occupy the interrupt number and I/ of other devices in the computer. O conflict. Select "REAL MODE AND ENHANCED MODE NDIS DRIVER" in "DRIVER TYPE".
In addition, if all computers cannot be connected properly, you should consider whether the server is working properly. First, consider whether the server hardware itself is faulty. Whether or not the WINDOWS NT operating system has been damaged. However, this situation is very rare.
In short, network faults are divided into hardware, software, and operations. The hardware failure mainly manifests as: HUB damage, network cable and RJ45 bad contact, network card damage or poor contact. Software faults mainly include: whether the network card settings are correct, whether the interrupt number and I/O are appropriate, and whether the network clients and protocol settings are incorrect. The operational problems are: The correct user name and password have not been entered.
In addition, you should pay attention to the daily maintenance of the network. If you fix the network cable, do not move the computer at random, pay attention to not affect the network cable when moving, normally exit WINDOWS, normal shutdown and so on.
Due to the variety of network failures, it is impossible to cover all aspects in this paper. There are areas that are not considered or are not suitable. Please criticize and correct me. From "Prepress Technology"
At present, the typesetting LAN is generally WINDOWS NT. It adopts a star topology and uses a twisted-pair RJ45 connector to connect with a work group or a domain (D0MAIN). The agreement adopts NETBEUI, IPX/SPX, TCP/IP and so on. Generally, this network is relatively stable, but after working for a period of time, various network failures may occur due to aging of the equipment. Below, I summarize the troubleshooting steps and ideas for practical problems.