DFS and UNC access

I have a situation with DFS that I need some assistance with.
First, a bit of background info.

I am attempting to setup two new W2k3 servers which replace my existing W2k
server. My infrastructure is:

Domain: tclafayette1
Old Server: TCW2KSRV1 - Secondary DC, Recently moved FSMO, GC to new server
TC1

New Server: TC1 - Primary DC, FSMO, GC, WINS, DNS, DFS master
New Server: TC2 - Secondary DC, WINS, DNS

On TC1 I have created a folder named Shared as a top level share, and setup
a DFS namespace as tclafayette1.local\shared. I also setup a folder named
Shared on TC2 as a top level share, and setup a root target in DFS. and
setup replication between the two systems. I created some subfolders and
files to test replication, and all is working fine!

TCW2KSRV1, my old server, has a top level share folder named Shared as well,
but I have NOT setup TCW2KSRV1 in DFS by any means.

The issue is that when attempting to access \\TCW2KSRV1\Shared, what gets
returned is the Shared dir from \\TC1 (also replicated on TC2). This happens
on any workstation or server in the domain, even when attempted on TCW2KSRV1
itself. Now when I connect my own notebook to the network (which does NOT
belong to this domain), and I access \\TCW2KSRV1\Shared, the correct set of
folders is returned. I can also access \\TC1\Shared and see the correct set
of folders and files.

On TCW2KSRV1, I have the entire C: drive being shared, where the Shared
folder resides, and accessing it as \\TCW2KSRV1\CDrive\Shared does return the
correct set of folders.

I even have stopped the DFS service on all systems, and the results are the
same.

So the question is why does accessing \\TCW2KSRV1\Shared from any domain
based station return what is defined in DFS. The only thing it could be is
that the Shared share is setup on all 3 servers and DFS takes precedence.
Is there any way to correct this?

Thanks in advance.

--
LThibx