Windows 2003 shared resource denied access resolution

In the daily maintenance of server data, the access of shared resources is especially important and the core of network communication. Http://www.aliyun.com/zixun/aggregation/11208.html ">microsoft Company's Windows 2003 The Remote Desktop Connection program brought by the server operating system provides us with a fairly convenient way to manage each network.

But recently I encountered in the day-to-day maintenance of the following problems, although not too many technical content, but think of network management brothers may often encounter a similar small problem, will be the whole troubleshooting process one by one, I hope to be a hint to you.

First of all, an account of the environment, a machine IP address of 192.168.0.1, as a Terminal server (storage access to the shared resources), and installed the rising anti-virus software and rising personal firewall; b Machine IP address is 192.168.0.2, as a Remote Desktop client (through the client access to a Terminal server shared resources), both computers are Windows 2003 server operating system, and the installation of Remote Desktop Connection, B machine has been able to remotely manage a machine, Access to shared resources on a machine hard disk by running \192.168.0.1\x$ (x as a letter) (add that, because Win2003 's Remote Desktop program defaults to remote control of the server, but cannot instantly copy the files on it, so the data is transmitted in this way).

One day, for a machine application rising antivirus software in the vulnerability scanner, in the security settings of the tip is the application of x$ access security is lower, can be automatically repaired, so did not want to determine the automatic repair, restart found that B-machine can not run through the \192.168.0.1\x$ access to a machine's shared resources , but Remote Desktop is still handy.

What's going on here? Recall just in addition to run rising antivirus program and no other operations, so from the anti-virus software to eliminate one by one, the modification of a machine set, B machine can not run \192.168.0.1\x$ through the way to a shared resource access to a machine. First suspected vulnerability patch modified Remote Desktop Connection program, so reinstall a machine Remote Desktop and Terminal Server program, the fault is still, so simply the B-Machine remote connection program also reinstalled again, or not.

Considering whether to disable access to shared resources on the command line, and then run net share x$ on a machine, enable sharing permissions on the X disk of machine A, or fail to access data by running \192.168.0.1\x$, the problem is still not resolved.

So back to the crux of the problem-rising antivirus software vulnerability scanner, recall the use of Skynet firewall when there is a similar security scanning program, that will be a machine on the rising personal firewall cut off access to data? So stop rising personal firewall, on the B machine running \ 192.168.0.1\x$, Haha, there are familiar password prompts, typing password, OK, a machine x disk data can finally be accessed!

This time, for the repair of shared resource access, although around a little corner, but also let me again familiar with the problem of remote access to the solution, in fact, the problem is very simple, easy to solve, but simple things often seem complex, I hope that friends encounter similar problems in the first time do not move, Finding the cause from the source, the problem will be solved easily, right?