Access denied, unable to connect: My Solution. (Win XP)

Halo All.

Ive seen many different causes to this problem, solutions as well.

Herewith the solution I used, and also what was causing it:

We're in the process of migrating our machines to XP. AD has been
implemented.

We had the problem of some machines added to our domain giving the
"Access denied, unable to connect" error. I searched high and low, but
none of the posts provided a resolution.

What caused this problem in the end in our case was a local computer
(Security Options) policy. Double check the following in these
policies (It must either be "Not Defined" or the following values must
be located in each of the three:

Located in local policy, security options > "Network Access:"

"Named pipes that can be accessed anonomously"
---------------------------------------------
COMNAP
COMNODE
SQL\QUERY
SPOOLSS
LLSRPC
EPMAPPER
LOCATOR
TrkWks
TrkSvr

"Remotely accessible registry paths"
--------------------------------------
System\CurrentControlSet\Control\ProductOptions
System\CurrentControlSet\Control\Print\Printers
System\CurrentControlSet\Control\Server Applications
System\CurrentControlSet\Services\Eventlog
Software\Microsoft\OLAP Server
Software\Microsoft\Windows NT\CurrentVersion
System\CurrentControlSet\Control\ContentIndex
System\CurrentControlSet\Control\Terminal Server
System\CurrentControlSet\Control\Terminal Server\UserConfig
System\CurrentControlSet\Control\Terminal
Server\DefaultUserConfiguration

"Shares that can be accessed anonomously"
------------------------------------------
COMCFG
DFS$

####################################################################

If unsure, you can also run the following command to reset all your
security settings on your workstation:

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb
/verbose