First, the source of the problem:
Dell5460 notebook on a winxp system virtual machine to access shared resources on a lenovoT470 Education Edition notebook win10 system (using the command line: net use s: \\ 172.18.45.105 \ d), always prompt "System error 64. the specified network name is no longer available. ", and dell5460 notebook win10 enterprise Edition to access its shared resources is normal.
Second, the process:
Education Edition tune in win10 and winxp system, many parameters can not solve the problem, then carefully think that should be associated with version smb protocol. Education Edition installed on a win10 machine wireshark capture tool, respectively crawl access its shared directory from winxp and win10 Enterprise Edition machine packets clearly see win10 Enterprise packets mainly SMB2 protocol packets, and the data winxp pack only SMB packet. Thus, the basic direction to determine the correct guess. Check the "Control Panel" - "Programs and Features" - "to enable or disable Windows features" in "SMB 1.0 / CIFS file sharing support" "SMB 1.0 / CIFS server" does not checked, the check is still no sharing success. Analysis because win10 supports smb1, smb2 and smb3, although smb1 support is on, but can not guarantee that the machine will request access to smb1 accordingly. Continue to find information on the Internet and found an article on the detection, for enabling and disabling smb1,2,3, and follow the instructions in this article, modify the registry in win10 Education Edition Microsoft official website, in the "HKLM: \ SYSTEM \ CurrentControlSet \ Services \ LanmanServer \ Parameters "in New" DWORD (32-bit) value ", named" SMB1 ", which is set to hex value" 1 "indicates a mandatory SMBv1 response protocol. You must restart the computer to take effect after the registry modification. After the restart, and then access shared resources from win10 Education Edition winxp, success! ! !
Third, the summary:
1, arguably, check function is enabled and closed windows in SMB 1.0 / CIFS server response after SMBv1 function should be enabled, however, the win10 Education Edition has not given a response to smbv1, only forced to respond by modifying the registry smbv1 protocol. This shows that the win10 version of education there should be some bug or limitation. After you configure smbv1 forced to respond, and then measuring win10 Enterprise Edition to access the shared directory win10 version of education, will not be affected, observed packet capture, packet win10 Enterprise Edition is indeed SMBv2 protocol packets. This shows that, win10 EDUCATION Although positive response to smbv1, for the smbv2 received packets can also be a normal response.
2, inspired by modifying the registry method to observe the win10 and win10 Enterprise Edition, Education Edition registry registry cases in: Enterprise win10 found more than two DWORD "HKLM \ SYSTEM \ CurrentControlSet \ Services \ LanmanServer \ Parameters" in value, as shown below:
Try win10 Education Edition machine registry by adding the same position as these two values, and then restart the computer to test for winxp shared access to education win10 version of success! This shows how AdjustedNullSessionPipes this project is to adjust the key option to receive each version of SMB packets.
3, in the win10 Education Edition machine, start with administrator privileges powershell, enter the command: Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol or Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol, you can see the situation smbv1 agreement, as follows:
PS C:\Windows\system32> Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
FeatureName : SMB1Protocol
DisplayName: SMB 1.0 / CIFS file sharing support
Description: Support SMB 1.0 / CIFS file sharing protocol and a computer browser protocol.
RestartRequired : Possible
State : Enabled
CustomProperties :
ServerComponent \ Description: support SMB 1.0 / CIFS file sharing protocol and a computer browser protocol.
ServerComponent \ DisplayName: SMB 1.0 / CIFS file sharing support
ServerComponent\Id : 487
ServerComponent\Type : Feature
ServerComponent\UniqueName : FS-SMB1
ServerComponent\Deploys\Update\Name : SMB1Protocol