I have Win2000 AD on my Environment.
I have configured a new CNAME record on my DNS and to point it to a host
called hosts.abc.org (win2003).
I can resolves the new CName perfectly.
However when I do \\cname.abc.org it gives me an error..
"you were not connected because of a duplicate name exists on the network"
I can do \\hosts.abc.org no problems but not on the alias.. As far as I know
I never use that name before.
How can I fix this??
thank you
Where it is???
I believe that there is a fix for this, but do not have it handy.
By default UNC only works with the hosts netbios name or IP address.
It is a security feature imposed by the remote host.
The server is seeing your request for cname and saying "That's not me, I'm hosts".
I believe that there is a setting on the remote host that turns off this checking.
cnames work fine for anything except CIFS (SMB) file sharing.
--
--
Steven
http://www.glimasoutheast.org
"Orvs" <Orvs@discussions.microsoft.com> wrote in message news:634E0F71-C926-47FF-992C-B53A75657E14@microsoft.com...
>I have Win2000 AD on my Environment.
>
> I have configured a new CNAME record on my DNS and to point it to a host
> called hosts.abc.org (win2003).
>
> I can resolves the new CName perfectly.
>
> However when I do \\cname.abc.org it gives me an error..
> "you were not connected because of a duplicate name exists on the network"
>
> I can do \\hosts.abc.org no problems but not on the alias.. As far as I know
> I never use that name before.
>
> How can I fix this??
>
> thank you
>
> Where it is???
>
>
>
>
>
"BerkHolz, Steven" <spamtrap@Astrumtech.com> wrote in message
news:Oih0aFvPHHA.4424@TK2MSFTNGP06.phx.gbl...
>I believe that there is a fix for this, but do not have it handy.
>
> By default UNC only works with the hosts netbios name or IP address.
> It is a security feature imposed by the remote host.
UNC names can (generally) works with DNS style names or even IP
addresses (as of NT4+ with IP loaded) but there are problems for
building multiple (CNAME style) alias different from the machines
ordinary name + domain name, for accessing Shares etc.
There is a fix for this -- it's a registry entry IIRC.
> The server is seeing your request for cname and saying "That's not me, I'm
> hosts".
> I believe that there is a setting on the remote host that turns off this
> checking.
> cnames work fine for anything except CIFS (SMB) file sharing.
The problem is not DNS names per se, but multiple names for shares etc.
net view \\Server.Domain.Com
....will generally works if this is the machines true name.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
H HErb can you please send me the workaround or the steps I need to do?
It is more clearer now..
"Herb Martin" wrote:
>
> "BerkHolz, Steven" <spamtrap@Astrumtech.com> wrote in message
> news:Oih0aFvPHHA.4424@TK2MSFTNGP06.phx.gbl...
> >I believe that there is a fix for this, but do not have it handy.
> >
> > By default UNC only works with the hosts netbios name or IP address.
> > It is a security feature imposed by the remote host.
>
> UNC names can (generally) works with DNS style names or even IP
> addresses (as of NT4+ with IP loaded) but there are problems for
> building multiple (CNAME style) alias different from the machines
> ordinary name + domain name, for accessing Shares etc.
>
> There is a fix for this -- it's a registry entry IIRC.
>
> > The server is seeing your request for cname and saying "That's not me, I'm
> > hosts".
> > I believe that there is a setting on the remote host that turns off this
> > checking.
> > cnames work fine for anything except CIFS (SMB) file sharing.
>
> The problem is not DNS names per se, but multiple names for shares etc.
>
> net view \\Server.Domain.Com
>
> ....will generally works if this is the machines true name.
>
> --
> Herb Martin, MCSE, MVP
> http://www.LearnQuick.Com
> (phone on web site)
>
>
>
Hi
Read
Connecting to SMB share on a Windows 2000-based computer or a Windows Server
2003-based computer may not work with an alias name
http://support.microsoft.com/kb/281308
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE
"Orvs" <Orvs@discussions.microsoft.com> wrote in message
news:87996B4F-B26D-43B2-A407-B2D033461784@microsoft.com...
>H HErb can you please send me the workaround or the steps I need to do?
>
> It is more clearer now..
> "Herb Martin" wrote:
>
>>
>> "BerkHolz, Steven" <spamtrap@Astrumtech.com> wrote in message
>> news:Oih0aFvPHHA.4424@TK2MSFTNGP06.phx.gbl...
>> >I believe that there is a fix for this, but do not have it handy.
>> >
>> > By default UNC only works with the hosts netbios name or IP address.
>> > It is a security feature imposed by the remote host.
>>
>> UNC names can (generally) works with DNS style names or even IP
>> addresses (as of NT4+ with IP loaded) but there are problems for
>> building multiple (CNAME style) alias different from the machines
>> ordinary name + domain name, for accessing Shares etc.
>>
>> There is a fix for this -- it's a registry entry IIRC.
>>
>> > The server is seeing your request for cname and saying "That's not me,
>> > I'm
>> > hosts".
>> > I believe that there is a setting on the remote host that turns off
>> > this
>> > checking.
>> > cnames work fine for anything except CIFS (SMB) file sharing.
>>
>> The problem is not DNS names per se, but multiple names for shares etc.
>>
>> net view \\Server.Domain.Com
>>
>> ....will generally works if this is the machines true name.
>>
>> --
>> Herb Martin, MCSE, MVP
>> http://www.LearnQuick.Com
>> (phone on web site)
>>
>>
>>
Jorge Hi!!
Thanks! But I tried and apply the registry set and still same, except when I
tried the \\aliasname.domin.com on the actual server itselt it works! but not
from any other machines
any other ideas?
"Jorge Silva" wrote:
> Hi
> Read
> Connecting to SMB share on a Windows 2000-based computer or a Windows Server
> 2003-based computer may not work with an alias name
> http://support.microsoft.com/kb/281308
>
>
> --
>
> I hope that the information above helps you.
> Have a Nice day.
> Jorge Silva
> MCSE
>
> "Orvs" <Orvs@discussions.microsoft.com> wrote in message
> news:87996B4F-B26D-43B2-A407-B2D033461784@microsoft.com...
> >H HErb can you please send me the workaround or the steps I need to do?
> >
> > It is more clearer now..
> > "Herb Martin" wrote:
> >
> >>
> >> "BerkHolz, Steven" <spamtrap@Astrumtech.com> wrote in message
> >> news:Oih0aFvPHHA.4424@TK2MSFTNGP06.phx.gbl...
> >> >I believe that there is a fix for this, but do not have it handy.
> >> >
> >> > By default UNC only works with the hosts netbios name or IP address.
> >> > It is a security feature imposed by the remote host.
> >>
> >> UNC names can (generally) works with DNS style names or even IP
> >> addresses (as of NT4+ with IP loaded) but there are problems for
> >> building multiple (CNAME style) alias different from the machines
> >> ordinary name + domain name, for accessing Shares etc.
> >>
> >> There is a fix for this -- it's a registry entry IIRC.
> >>
> >> > The server is seeing your request for cname and saying "That's not me,
> >> > I'm
> >> > hosts".
> >> > I believe that there is a setting on the remote host that turns off
> >> > this
> >> > checking.
> >> > cnames work fine for anything except CIFS (SMB) file sharing.
> >>
> >> The problem is not DNS names per se, but multiple names for shares etc.
> >>
> >> net view \\Server.Domain.Com
> >>
> >> ....will generally works if this is the machines true name.
> >>
> >> --
> >> Herb Martin, MCSE, MVP
> >> http://www.LearnQuick.Com
> >> (phone on web site)
> >>
> >>
> >>
>
If I'm not mistaken here it goes:
(DisableStrictNameChecking to 1)
Second:
set on a DC:
SetSpn -A HOST/<ALIAS> <Hostname>
SetSpn -A HOST/<ALIAS>.<Domain>.<ext> <Hostname>
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE
"Orvs" <Orvs@discussions.microsoft.com> wrote in message
news:4A5D4555-2D14-4AEC-8289-8173BF24C85A@microsoft.com...
> Jorge Hi!!
>
> Thanks! But I tried and apply the registry set and still same, except when
> I
> tried the \\aliasname.domin.com on the actual server itselt it works! but
> not
> from any other machines
>
>
> any other ideas?
>
>
> "Jorge Silva" wrote:
>
>> Hi
>> Read
>> Connecting to SMB share on a Windows 2000-based computer or a Windows
>> Server
>> 2003-based computer may not work with an alias name
>> http://support.microsoft.com/kb/281308
>>
>>
>> --
>>
>> I hope that the information above helps you.
>> Have a Nice day.
>> Jorge Silva
>> MCSE
>>
>> "Orvs" <Orvs@discussions.microsoft.com> wrote in message
>> news:87996B4F-B26D-43B2-A407-B2D033461784@microsoft.com...
>> >H HErb can you please send me the workaround or the steps I need to do?
>> >
>> > It is more clearer now..
>> > "Herb Martin" wrote:
>> >
>> >>
>> >> "BerkHolz, Steven" <spamtrap@Astrumtech.com> wrote in message
>> >> news:Oih0aFvPHHA.4424@TK2MSFTNGP06.phx.gbl...
>> >> >I believe that there is a fix for this, but do not have it handy.
>> >> >
>> >> > By default UNC only works with the hosts netbios name or IP address.
>> >> > It is a security feature imposed by the remote host.
>> >>
>> >> UNC names can (generally) works with DNS style names or even IP
>> >> addresses (as of NT4+ with IP loaded) but there are problems for
>> >> building multiple (CNAME style) alias different from the machines
>> >> ordinary name + domain name, for accessing Shares etc.
>> >>
>> >> There is a fix for this -- it's a registry entry IIRC.
>> >>
>> >> > The server is seeing your request for cname and saying "That's not
>> >> > me,
>> >> > I'm
>> >> > hosts".
>> >> > I believe that there is a setting on the remote host that turns off
>> >> > this
>> >> > checking.
>> >> > cnames work fine for anything except CIFS (SMB) file sharing.
>> >>
>> >> The problem is not DNS names per se, but multiple names for shares
>> >> etc.
>> >>
>> >> net view \\Server.Domain.Com
>> >>
>> >> ....will generally works if this is the machines true name.
>> >>
>> >> --
>> >> Herb Martin, MCSE, MVP
>> >> http://www.LearnQuick.Com
>> >> (phone on web site)
>> >>
>> >>
>> >>
>>
Assuming this is a member server, disabling strict name checking and
then rebooting should make it work fine as long as name resolution is
working and there is no funky routing rules/acls. I would recommend
getting a network trace to validate what is happening.
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
Orvs wrote:
> Jorge Hi!!
>
> Thanks! But I tried and apply the registry set and still same, except when I
> tried the \\aliasname.domin.com on the actual server itselt it works! but not
> from any other machines
>
>
> any other ideas?
>
>
> "Jorge Silva" wrote:
>
>> Hi
>> Read
>> Connecting to SMB share on a Windows 2000-based computer or a Windows Server
>> 2003-based computer may not work with an alias name
>> http://support.microsoft.com/kb/281308
>>
>>
>> --
>>
>> I hope that the information above helps you.
>> Have a Nice day.
>> Jorge Silva
>> MCSE
>>
>> "Orvs" <Orvs@discussions.microsoft.com> wrote in message
>> news:87996B4F-B26D-43B2-A407-B2D033461784@microsoft.com...
>>> H HErb can you please send me the workaround or the steps I need to do?
>>>
>>> It is more clearer now..
>>> "Herb Martin" wrote:
>>>
>>>> "BerkHolz, Steven" <spamtrap@Astrumtech.com> wrote in message
>>>> news:Oih0aFvPHHA.4424@TK2MSFTNGP06.phx.gbl...
>>>>> I believe that there is a fix for this, but do not have it handy.
>>>>>
>>>>> By default UNC only works with the hosts netbios name or IP address.
>>>>> It is a security feature imposed by the remote host.
>>>> UNC names can (generally) works with DNS style names or even IP
>>>> addresses (as of NT4+ with IP loaded) but there are problems for
>>>> building multiple (CNAME style) alias different from the machines
>>>> ordinary name + domain name, for accessing Shares etc.
>>>>
>>>> There is a fix for this -- it's a registry entry IIRC.
>>>>
>>>>> The server is seeing your request for cname and saying "That's not me,
>>>>> I'm
>>>>> hosts".
>>>>> I believe that there is a setting on the remote host that turns off
>>>>> this
>>>>> checking.
>>>>> cnames work fine for anything except CIFS (SMB) file sharing.
>>>> The problem is not DNS names per se, but multiple names for shares etc.
>>>>
>>>> net view \\Server.Domain.Com
>>>>
>>>> ....will generally works if this is the machines true name.
>>>>
>>>> --
>>>> Herb Martin, MCSE, MVP
>>>> http://www.LearnQuick.Com
>>>> (phone on web site)
>>>>
>>>>
>>>>
You really shouldn't have to set SPNs for this.
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
Jorge Silva wrote:
> If I'm not mistaken here it goes:
>
> (DisableStrictNameChecking to 1)
>
> Second:
> set on a DC:
> SetSpn -A HOST/<ALIAS> <Hostname>
> SetSpn -A HOST/<ALIAS>.<Domain>.<ext> <Hostname>
>
>
Posting Permissions
Reply With Quote
Bookmarks