Today I found a interesting bug in Windows Lan Manager Server service. We had renamed a server running Windows 2000 Server and created a DNS (CNAME) alias record for it because we wanted to be able to access the server both the new name and the old name. The new name works as it should but when we tried to access the server with its old name we wasn’t able to access.
At the command prompt “net view \\aliasname” -command gave an “System error 52 has occurred. duplicate name exists on the network” error which led me on false path, so first I was browsing the DNS server for false or loose records.
After some googling I found out that it’s a Microsoft bug (KB281308). The server is not listening on the alias name and therefore it is not accepting connections. Luckily there is a fix which solves this issue (see the KB-article for more details):
Note: Operations are made on the file server (not on the DNS server).
1. Apply the latest service pack.
2. Apply the following registry change
2.1 Start registry editor and locate following key:
2.2 Create a new value with following details:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
3. Reboot the server
After this addition in the registry the shares are available also with the old server name. The same fix applies to the Windows 2003 server.