Yea, I started thinking about that afterwards.
Wasn't there a registry tweek that would overcome [at least] some of those
things?
I guess it would be better to just rename the machine and forget it.
--
Phillip Windell
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"kj [SBS MVP]" <> wrote in message
news:...
> As I recall when attempting to connect \\cname\sharename you get a
> "duplicate names exists on the network error"
>
> Also doesn't work for connections that use certificates like secure ldap.
> (The computer connection needs to match the certificate)
>
> Probably a few other things as well that don't work.
>
>
> Phillip Windell wrote:
>> I don't know.
>>
>> But it is easy to try and find out.
>>
>>
>>
>> "Grant Taylor" <> wrote in message
>> news:i01fta$jp7$...
>>> Phillip Windell wrote:
>>>> Create a CNAME in DNS that point to the existing "A" Record.
>>>
>>> Will that work for things like UNC shares?
>>>
>>> I thought there was a setting somewhere that dictated if a CNAME
>>> would work or not. Is that not the case?
>>>
>>> I know the CNAME can be used to resolve the host name to an IP. But
>>> will File and Print Services (SMB/CIFS) be happy?
>>>
>>>
>>>
>>> Grant. . . .
>
> --
> /kj
>
|