Added CNAME in DNS but get "duplicate name exists on network" when accessing server
Hi,
I am replacing our Windows 2003 file server with a Windows 2008 R2 server. I have followed the registry change below to allow this server to be accessed (via SMB shares and drive letters) from XP and above machines:
Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
Apply the following registry change to the file server. To do so, follow these steps:
Start Registry Editor (Regedt32.exe).
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
On the Edit menu, click Add
Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
Quit Registry Editor.
Restart your computer.
It didn't work so on the new file server I also tried:
setspn
-a host/newservername oldservername
It
seems Windows 7 PC's can access the servers drive letters and shares using the CNAME but XP users can't.
What
can I do?
Thanks
September 19th, 2010 4:41am
Hi,
the warning "duplicate name exists on network" has nothing to do with DNS server, this warning is sent by NetBIOS thus duplicate name is registered or in WINS server or in server that is elected as master browser.
To resolve this issue follow this KB article
http://support.microsoft.com/kb/822659/en-us
HTHEdoardo Benussi - Microsoft MVP
Management Infrastructure - Systems Administration
https://mvp.support.microsoft.com/Profile/Benussi
Windows Server Italian Forum Moderator
edo[at]mvps[dot]org
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2010 6:52am
Use this registry setting
OptionalNames: can be either Reg_SZ or Reg_Multi_SZ
Add one or more names and restart the server service.
This action registers the names in Windows Internet Name Service (WINS)
If the "optionalname" was a pervious computer you must must delete the computer
account in AD. Otherwise the following error message will appear when
attempts to connect a share are made.
Login Failure: The target account name is incorrect.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"OptionalNames"
More info
http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/e6a5f937-d51b-43c8-b94f-7f24c100b935
September 19th, 2010 10:39am