What should I do if win2000 is stuck in Preparing for network connection and cannot enter the syst

I don't think this has much to do with the Netlogon service.

Not only can't you enter the system in normal mode, but also can't enter the system in safe mode, which means that there must be something wrong with your system, and you mentioned the update patch in the supplement! Is there something unfinished at the time of the update? Or the update failed? and cause damage to the system.

I think the best solution is to reinstall the system like everyone else.

I've had a similar problem, I can't get in.

The reason is that the system files are corrupted while you are antivirus.

You can fix it with the system disk.

To repair, you have to first select Install Windows and then Repair. The direct repair is to use the console or use the repair disk, if you don't have it or don't know how to use it.

After the repair is completed, all the software, registry, and drivers are still intact!

It may be that there is a virus in your computer system, and you enter the safe mode of the system to kill the virus, or it may be that the system has not been maintained for a long time, and your system files have been lost. This is good for the system and convenient for you to use!

One question:"I entered the safe mode, and after entering the password, I was prompted with "You cannot log in because the Netlogon service is not running on the machine"."

This is mainly a service that is not open. That is, you said "netlogon", you can open it in the service (to the service of the management tool in the control panel, press the letter n to see the netlogon service, and then right-click to start it) netlogon service: support the pass-through account login authentication event of the computer on the network.

Question 2: What should I do if win2000 is stuck in "Preparing for network connection" and cannot enter the system when starting? I've had this happen before, but I was able to restart it (it got stuck again the next day), so I reinstalled the system.

Because the system files are corrupted, it is recommended to reinstall the system, or you can use the system disk to repair.

Use the Optimizer System Cleanup & Maintenance System Disk Doctor: Selected System Disk to check. You need to insert the installation disk into the optical drive to mate, try it.

I think the only way to reinstall the system is to lose the system and not be able to start.

Enter the system in safe mode and set the Netlogon service to start when it is turned on.

There is something wrong with Rising, my classmate used to install 2005, and he installed the system card to death, and reinstalled it.

The younger brother offers a trick:

Unplug the network cable and turn it on, and enter the plug-in.

Or fix down the IP

This eliminates the need for detection at boot

1. Set the system boot to CD-ROM boot and repair it with the system disk. The specific repair method is similar to the installation system, and pay attention to the options in the process, which is to install and repair.

2. It is best to reinstall the system, so that the system should be more stable.

on other machines.

NextIPS's antivirus-specific job. You boot into safe mode for antivirus. And then just come in.

It is better to reinstall the system.

Netlogon service?

Can't even enter safe mode?

Network login? Disconnect from the network and give it a try.

Aren't there several options for trying other security modes?

At present, win2000 users have been very rare, it is recommended that you change to a more advanced XP 7 8 and other operating systems.

There are still some problems with the compatibility of the PE system, and I have tried several configurations of computers that can't enter PE or the process of entering PE is extremely slow. Try to run ghost manual recovery directly under the DOS system, ghost has a strong ability to search for image files, even if it is saved in a hidden partition, it can be dug out.

What year did you buy that computer?,Still use the 2000 system.,You can't get into PE with a CD.,It's estimated that there's something wrong with the motherboard.,It's recommended to change it.。。。

It's the same way to find fault.,It's troublesome.。。

Backup file is corrupted, reinstall the system.

I've tried several configurations of computers that can't get into PE

Generally, the server boots up very slowly.

This situation is the most speechless. There are three main points: 1. There are too many network protocols or driver libraries of the system platform loaded on the server; Clean-up and optimization measures need to be done; 2. When the network line where the server is located responds too slowly, or does not respond, or is abnormal, it is often stuck in this link.

3. Especially for the win2003 server machine with AD domain, it is slower to load the network protocol.

It seems that it can't be eliminated.,Windows2000When you boot up,This window generally appears.,After all the tests are completed,It can be started normally.。

It seems that adding a domain will become very slow to boot and shut down......

I'm a little unclear about this! In my previous company, there was an IBM server that was not in the domain, and it took more than five minutes to boot up! Server companies are saying it's normal! I've only played 2003 on a virtual machine, and it's so slow to enter the domain! Especially the shutdown! I'm.

You set up Active Directory, domain controller, set up DNS, and 5-15 minutes is the normal range. I think your last words are the key "so many account resets are quite troublesome", the more users and configuration information the more complex and slow.

Also, see if there are any valuable hints in the Event Viewer.

You set the network connection to a manual connection, which means that you go to the desktop first, and then manually double-click the network connection icon to connect.

Is this the first time you've heard that the NIC driver is in conflict with the system? It's impossible, is there a Trojan or software that starts with the network, when the network is connected, they start to work, and the memory is full, so that the desktop (because there is no memory can not run on the card, you should go to the startup items to see, and disable the startup items that you don't want.)

You may have plugged your router and other network equipment incorrectly.

Mark it and learn.

Once in the past, I always had to disable the NIC in safe mode before entering. Later, it seems that the driver of the network card was reinstalled, and it took a day.

Let's see if we can learn an easy way.

It's so complicated, just reinstall the system and try it. You don't have to toss around like this.

First of all, before the "Startup" interface, press F8 to enter the advanced startup menu and select "Last Correct Configuration" to see, if not.

Select "Repair System" to take a look.

If it doesn't work, go into safe mode.

Some systems have this situation due to software reasons.

Scenario 1: For example, the service eventlog is disabled.

Solution: Right-click on My Computer - Management - Services - Find eventlog - Set to Auto Restart Situation 2:

And what I've seen is software conflicts, for example, someone has two antivirus software conflicts.

If this is the case, enter safe mode and uninstall one to do so

In fact, many people will have this situation, hardware problems.

The general "Booting" screen is when Windows detects the hardware if there is a problem with your hardware.

There is a good chance of stopping.

The solution is, think about whether you have recently changed the driver? Did you add new hardware? If so, replace the driver or uninstall the hardware.

If not, try it with the last correct configuration.

1. After the computer starts, it has been stuck in the "Starting Windows" interface. 2. This kind of problem is very common, the computer version of the system is not compatible, and the general green lite version of the system is prone to this kind of problem. 3. Press Ctrl+Alt+del to automatically restart the computer before entering the "Starting Windows" interface.

It's the same with the laptop I encountered.,Win7 system,I've never been like this before reinstalling the system.,I installed the system instead.,Later, I changed the hard disk.,It's not okay to change other systems.,Finally, it's okay to flash the BIOS.。

It should be caused by what you installed, whether you installed other cards or settings on the server, try to take it down.