Solve the strategy that Win2003 shared resources cannot be accessed

The system used is Win2003. Today, after viewing "Local Sharing" in "Computer Management", the error dialog box will pop up "The server service is not started". What kind of prompt is there? Strategy to solve it?

First of all, let's explain the environment, the IP address of machine A is 192.168.0.1, as the terminal server (storing the shared resources accessed), and installed Rising antivirus software and Rising personal firewall; B The IP address of the machine is 192.168.0.2, which is used as the client of the remote desktop (through the client to access the shared resources on the A terminal server). Both machines are windows2003server operating system, and the remote desktop connection is installed. The B machine can always pass. The program remotely manages the A machine and accesses the shared resources on the hard disk of the A machine by running 192.168.0.1x$ (x is the drive letter). (Additionally, since the remote desktop program of win2003 is set to be remotely controlled by default The server, but cannot copy the files on it immediately, 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.1x$, 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 192.168. The .0.1x$ 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 netsharex$ 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.1x$, repeatedly restarting Did 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.1x$ 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 be accessed. !

The above steps are for the restoration of shared resource access. Maybe you will find the steps a bit cumbersome, but you can know the process of the whole problem in great detail. In fact, the problem is very simple, and the solution is very easy, but the simple problem is often complicated. I hope that when users encounter this problem, they must first find the reason from the source. I hope to help everyone.