lark2056

Hello

I have a file server with attached storage volumes set up as shared volumes on my network. For examples sake, I will make up the names as to not give out company data, not that anyone cares.

Server name is = test1

IP address = 10.41.240.100

domain is = bluethunder.com

volume 1 is shared with the share name as file1. I have given full rights to this share to the everyone group and security is set for everyone to have full access. This server is a windows server 2008 enterprise 64bit.

I have 3 domain controllers that area all virtual machines that run windows server 2008 standard 32 bit. They are all active directory integrated and they host my DNS as well.

I have an alias on my DNS that points to the file1 share

So I created a host (A) record on the bluethunder.com domain called
file1.bluethunder.com with the IP of 10.41.240.100. nice and neat.

If I go to a windows server 2008 box in that domain and type in
\\file1.bluethunder.com\file1 from a run box it opens just fine

If I am at a windows 2003 server in the same domain and I type the same thing at a run box I get

"You were not connected becasue a duplicate name exists on the network. Go to system in control panel to change the computer name and try again."

This happens EVERY TIME!! I think I have tried EVERYTHING to fix this to no avail.

If I type in \\10.41.240.100\file1 from the run box in the windows server 2003 box it works just fine. So I know it is something to do with the name.

I have done some searching and everything points me to microsoft knowlege base article 281308. I tried to add this disable strict name checking registry hack to the file server but it hangs everytime I try to reboot it with the fix. I have to go to last known good config to get the file server back up and the registry hack is gone. So the file server does not like it at all.

I am at my wits end with this one. Any other ideas would be beyond appreciated. Thanks!!

lark2056