The gray user name for accessing WINXP cannot be changed | cancel simple file sharing

The gray user name for accessing WINXP cannot be changed | cancel simple file sharing

The gray user name for accessing WINXP cannot be changed | cancel simple file sharing. The default Administrator of the customer's network administrator who wants to access other machines in the same LAN. For example, enter // 192.168.0.100/e $. In the pop-up window, only the User Name of the Guest account is displayed, and the Administrator account cannot be selected. In the connection dialog box, the User Name box displays the Guest account, which is gray and cannot be changed. How to fix it.

Answer: perform the following actions on the machine 192.168.0.100:
1. Open the Resource Manager
2. Select the folder option in the tool menu.
3. Click View-advanced options
4. deselect "simple file sharing ".
5. OK.

For detailed principle analysis, see the following description: (the original author is the Windows itpro Asia Technology Forum .)Blackbird,Then it is sorted by gnaw0725. The article you see originates from the Active Directory Seo http://gnaw0725.blogbus.com)
I used to see many connection and login issues related to XP in the previous Forum (most of them are similar to win2003). I would like to make a brief summary over the weekend. I would like to add some shortcomings.

(1) the error message "unauthorized user request login type on this computer" (LOGIN by Win2000 WINXP/win2003) is always displayed. The error message "no resource access permission" (LOGIN by Win98) is displayed)

Cause: it is caused by the user permission of guest in the policy that is forbidden to log on from the network, and the error mentioned in (2. (Note: XP default, win2003 not default)

Solution: configure the Local Security Policy:/Security Settings/Local Policy/user permission assignment/"Deny access to this computer from the network", and delete and save the guest.

(2) by default, the system logon window is logged on as a guest user and cannot be changed.

Cause: it is because the "local account sharing and security mode" in the XP security policy for network access is verified by default by a local user as a guest, that is, they are treated equally, all visitors are "guests ". (For example, after XP is added to the domain, local users are authenticated by default, and interactive logon such as telnet and terminal service logon is invalid) (Note: XP is the default, win2003 is not the default) the article you see originates from the Active Directory Seo http://gnaw0725.blogbus.com

Solution: Open the Local Security Policy/Security Settings/Local Policy/security options/and change the policy settings.

(3) The logon window appears, but no user can log on.

Cause: the Guest account is disabled, and the "Network Access: sharing and security mode of the Local Account" security option is set to "Guest only ". In this case, the network logon performed by the Microsoft Network Server (SMB Service) will fail. Even if you know that the administrator user and password are useless, no response is made to all logins. (This case seems to involve a large number of people)

Solution: Change the prohibitions mentioned above. For example, activating a guest user and setting "Sharing and security modes of Local Accounts" to Classic mode.

(4) There is a logon window to know the administrator username and password of an XP project. The password is blank (the establishment user of XP during installation does not prompt to create a password), but cannot log on. There is always an error message "User Account restriction", and a similar prompt appears in the logon terminal service.

Cause: For security reasons, the Local Security Policy defaults to "only allow Console Logon for a local account with a blank password", that is, only local logon is allowed, ^ e ^ ~ ''Can only be logged on through the keyboard that connects to the computer. It cannot be logged on in non-physical contact mode. Some people may say that I tried to log on with a user with an empty password. ^ E ^ ~ 'That's because the Guest user is not forbidden. After your login to this user fails, the user will automatically use the guest user to try it. If the sharing is permitted, the user can log on. Otherwise, the user will not be able to log on. The article you see originates from the Active Directory Seo http://gnaw0725.blogbus.com

Solution: Enable the Local Security Policy/Security Settings/Local Policy/security options/and disable the settings. We recommend that you keep the default security settings.

Gnaw0725 Note: I will add four more points:
(5) If the share you created on WINXP is shared by the root directory of the disk, the share is a remote management share. Only the Administrator account can be remotely connected, and the normal account can be connected, the system will prompt that the access is rejected. For more information about creating shares on WINXP, see http://support.microsoft.com/kb/304040/zh-cn.

(6) Internet firewall may block browsing and file sharing. Do not use a firewall on a network connection that is connected to a home or office network, or enable browsing and file sharing in the "exception" section of the firewall settings

(7) If there is a problem with the TCP/IP component and related network component files, the remote connection will prompt that the network path cannot be connected.
A computer with the same name may exist in the network. You can try to change the computer name.
Or the current computer is Ghost, but no sysprep operation is performed to extract hardware information. You can try the sysprep operation again.
Or the TCP/IP component and related network component files are lost. You can try to reinstall all network components and fix the installation.
Or the network component disk file is damaged. You can try chkdsk/R.

(8) If it is a domain controller, the stop of the netlogon service will also impede remote access. Start the service and check the cause of the startup exception .)

:(~~ 'The funny thing is, Microsoft said that the remote interactive login application "may" ignore this setting, and this setting does not affect login using domain accounts. The article you see originates from the Active Directory Seo http://gnaw0725.blogbus.com

In summary, XP has made more efforts in terms of security, and it is not suitable for 2000 of users at the moment. However, XP has come up with some convenient methods for us, but many of our friends have not used them. Because XP is used by default for your personal use and does not connect to the network. When you want to connect to the network, as long as you run the "Network Installation Wizard", during this wizard, it will open several prohibited items of XP by default (for example, guest activation and deleting from the list of network logins in the Policy), and when you are in the folder property, remove the default "use simple file sharing" option of XP, as mentioned in (network access: the "share and security mode" security option of the local account is set to "Guest only". The setting is also changed to the classic mode. Therefore, we recommend that you use this installation wizard and some frequently used attribute settings to restore the commonly used 2000 network connection. The so-called security policies only focus on the centralized performance and management of these settings. I hope you can combine the problems and solutions mentioned above to solve the problems encountered in your XP connection.