Win 2003 Shared Resource Prompt Denies Access to Troubleshooting Process

Between the computer and the computer, you can ping, but you can't access the shared resources. After viewing “Local Share” in “Computer Management”, the error message dialog box will pop up, “The server service is not started”, this appears. How to fix it? Recently, Xiaobian encountered similar problems in daily maintenance. Although there is not much technical content, I think that the network management brothers may encounter similar small problems, and the whole troubleshooting process will be eliminated. Come together, I hope I can give you some tips.

First of all, let's explain the environment. The IP address of the A machine is 192.168.0.1, as the terminal server (storing the shared resources being accessed), and the Rising antivirus software and the Rising personal firewall are installed. The IP address of the B machine is 192.168.0.2, as the client of the remote desktop (through the client to access the shared resources on the A terminal server), both machines are windows 2003 server operating system, and the remote desktop connection is installed, the B machine can always be remotely through the program Manage A machine, by running \\192.168.0.1\\x$ (x is the drive letter) to access the shared resources on the A machine hard disk (additional, because win2003 remote desktop program is set to remotely control the server , but the file on it cannot be copied instantly, so the data is transmitted in this way).

One day, after applying the vulnerability scanner in Rising Antivirus software to A machine, the security setting item prompts that the application x$ access is less secure and can be automatically repaired, so I don't think much about it. Automatic repair, restart found that the B machine can not access the shared resources of the A machine by running \\192.168.0.1\\x$, but the remote desktop is still easy to use.

What's the matter? I don't think there is any other operation except the Rising anti-virus program. So I started troubleshooting the anti-virus software one by one. After the modification of the A machine setting, the B machine could not run. The 192.168.0.1\\x$ method accesses the shared resources of the A machine. First, I suspected that the vulnerability patch modified the remote desktop connection program, so I reinstalled the remote desktop and terminal server program of the A machine. The fault persisted. I simply reinstalled the remote connection program of the B machine again, or it was not good. Considering whether the shared resource access is disabled by the command line, then running net share x$ on the A machine, enabling the sharing permission of the x drive of the A machine, or accessing the data by running \\192.168.0.1\\x$ Repeated restart still does not solve the problem.

So returning to the crux of the problem--the vulnerability scanning program of Rising Anti-Virus, recalling that there was a similar security scanner when using Skynet Firewall in the past, would it be the Rising Personal Firewall on the A machine? Cut off the way to access the data? So stop the Rising personal firewall, run \\192.168.0.1\\x$ on the B machine, haha, there is a familiar password prompt, knock the entry order, make sure that the data under the A machine x disk can finally Visited!

This time, the repair of shared resource access, although it is a little bit of a bend, but also let me re-familiarize the solution to the problem often encountered in remote access, in fact, the problem is very simple, solve It's easy, but simple things often seem complicated. I hope that when friends encounter similar problems, don't act rashly. Look for the cause from the source, the problem will be solved easily, isn't it?