If configured correctly, Windows 2003 will respond to aliases, CNAME’s, multiple names, etc. But this is broken as of SP1…
http://www.mcse.ms/archive183-2005-5-1632584.html
Yep found an answer.
1. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
2. Add Value
Value name: DisableLoopbackCheck
Data type: REG_DWORD
Radix: Decimal
Value: 1
“Thierry Van de Vaerd” <thierry.vandevaerd@telenet.be> wrote in message
news:uYa5FvVYFHA.2348@TK2MSFTNGP14.phx.gbl…[vbcol=seagreen]
> Hi,
>
> I’ve the same problem. I defined the key DisableStrictNameChecking like
> written in KB281308, and without Windows 2003 SP1, all worked fine.
> After installing SP1, I can connect to the alias share from all machines,
> but not from the server itself.
>
> any suggestions?
>
> “James Whitehead” <James@nocompany.com> wrote in message
> news:%23twsgiBYFHA.712@TK2MSFTNGP14.phx.gbl…
>
Just a note: You still need the DisableStrictNameChecking option defined, this article just means you have a second hack as well:
On an unservicepacked Windows 2003 if you had a DNS alias or local hosts
entry pointing to a server under the name “test.mydomain.com” it was
possible to access file shares on that server using the syntax
\\test.mydomain.com\c$ even though test.mydomain.com was not the real name of
the computer.
To make this work it was necessary to set the registry key
HLKM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\DisableStrictNameChecking to 1 (DWORD)
However, once service pack 1 is applied this no longer works. This means it
is not possible to open any ASP.NET projects in visual studio that do not use
‘localhost’ or the real computer DNS name once the service pack is applied.
