win2003 LAN issues

Just set a password for the machine you want to access.

Let's start with the network architecture...

If you can't share it, please refer to the following settings:

After setting the password, go to Start-Run-Enter "Open Group Policy, Windows Settings - Security Settings:."

1. Network access: The sharing and security model of the local account - set to "classic: authenticate the local user without changing their original identity. ”

2. Account: Local accounts with blank passwords are only allowed to log in to the console - set to: disabled 3. Account: Guest account status - set to "Enabled".

1. Access this computer from the network - add "everyone" or "guest".

2. Refuse to access this computer from the network - delete "guest".

Caused by not having the "Microsoft Network Client" installed. In the General tab of the Local Connectivity Properties window, make sure that Microsoft Network Client is selected, and then re-domain joining.

The "Microsoft Network Client" is one of the components that a client computer must have when adding a domain that allows the local computer to access resources on the Microsoft network. If you do not check this option, your local computer does not have an available tool to access the Microsoft network, resulting in a prompt that the network path cannot be found. The solution to the fault in this example is to inspire the user to install common components and protocols for the system to avoid many network failures, as shown in the figure.

1. I don't know if you have installed a domain controller, but it is recommended that you do not install it now, it is very complicated to set up, and it is recommended that you check the relevant information before using it!

ADSL: You make sure that your dialing is not set up incorrectly, and whether the relevant protocols are fully installed! Also, don't use your system as a workgroup member during installation!

2. You can cancel, but it is not recommended to do so, there will be security problems or cause system errors, the method can be found on the Internet, remember to set it in the group policy!

3. If you are familiar with 2003, it is recommended to use NTFS, if you are not familiar with it, use F32, the remote management tool must be installed under NTFS, if you use NTFS, you will be asked to set various permissions, the method is: run cmd, go to the drive letter to be converted, and execute covert x: fs:

NTFS can also be used with the help of third-party software, such as PQMoster

4. It is estimated that it is because of the shutdown tracking program in 2003, you go to the middle to turn off the shutdown tracking and try it!

If it is helpful to you, please remember to accept it as a satisfactory answer, thank you! Have a great day!

vae la

Try setting the IE security level to low.

There are no viruses on this unit, and of course there are no antiviruses.

IP conflicts are nothing more than two scenarios.

1.If the IP address of the computer is the same as this IP, it is a conflict.

2.Internally, there may be cyber enforcement officers targeting server attacks. The Cyber Enforcement Officer has this function, which is ostensibly to give IP conflicts that the computer cannot be used normally in the network. You try it with a cyber enforcement officer and see who is deliberately trying to fix you.

There is also the question of Hunger sharing, if you want to share it for internal use, the guest account can be banned.

If you say to someone who is on the Internet, as long as your machine is connected to the Internet, there is no possibility that it will not be invaded, so as long as you go online, others will be able to see what you share. You can see it, others can view it!