From: Phillip Windell on
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]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote in message
news:uTy2ZyHFLHA.5448(a)TK2MSFTNGP06.phx.gbl...
> 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" <gtaylor(a)riverviewtech.net> wrote in message
>> news:i01fta$jp7$1(a)tncsrv01.tnetconsulting.net...
>>> 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
>


From: kj [SBS MVP] on
Phillip Windell wrote:
> Yea, I started thinking about that afterwards.
> Wasn't there a registry tweek that would overcome [at least] some of
> those things?

Hmm. Maybe for the share name, but pretty sure it's "sorry charlie" for
anything using a cert.

>
> I guess it would be better to just rename the machine and forget it.
>
>
>
> "kj [SBS MVP]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote in message
> news:uTy2ZyHFLHA.5448(a)TK2MSFTNGP06.phx.gbl...
>> 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" <gtaylor(a)riverviewtech.net> wrote in message
>>> news:i01fta$jp7$1(a)tncsrv01.tnetconsulting.net...
>>>> 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

--
/kj


From: Grant Taylor on
kj [SBS MVP] wrote:
> Hmm. Maybe for the share name, but pretty sure it's "sorry charlie"
> for anything using a cert.

What about a cert that is using a SAN? Or a wild card cert for multiple
systems with in a domain?



Grant. . . .
First  |  Prev  | 
Pages: 1 2
Prev: Print Server reporting
Next: .msi File Editing