Server access FAQ
1. Q: the server cannot be pinged (172.20.43.49)
A: You cannot ping the server. There are two possibilities:
I. The IP Address Mask setting should be 255.255.252.0. The company uses the Intranet management client to forcibly change it to 255.255.255.0.
Manual modification may fail. Run the following command:
Assume that your Nic name is "Local Connection" and your IP address is "172.20.42.233 ".
Netsh interface IP Set address name = "Local Connection" static 172.20.42.233 255.255.252.0 172.20.40.1 1
2. unable to access the server due to ARP attacks, apply the following command to manually bind ARP:
ARP-s 172.20.43.49 00-91-50-08-11-a3
Set ARP binding in win7 to be under the Administrator account
Netsh interface IPv4 set neighbors 12 "172.20.43.49" "00-91-50-08-11-a3" store = persistent
2. Q: the server cannot be accessed using \ 172.20.43.49 \. The system prompts that the network path cannot be found.
A: You can use file: // 172.20.43.49/IPC $ or \ 172.20.43.49 \ personal document
The general method is: (here, the account Ding huifang and the password aoy8kn should be replaced with your own account and password)
Net use \ 172.20.43.49 \ IPC $12345/User: Zhang Xiaofeng/persistent: Yes
If the prompt is:
"A single user cannot use more than one user name to connect to the server or shared resource. This server is interrupted or
And try again. .
You can log out and log on to the system again, or close all connection windows to this service, and run the following command:
Net use file: // 172.20.43.49/IPC $/del
3. Q: Some directories cannot be written.
A: Make sure you use the correct account to log on. Anonymous Logon or incorrect account logon often results in this problem.