Aliases (CName) are not working

I'm trying to set up some DNS aliases (CName records) on a Windows
2000 / 2003 network. On one of the DNS servers I have a server named
Server1 (FQDN: Server1.Domain1.com)

In the DNS consol I create a CName record as follows:

Data1.Domain1.com

This points to Server1.Domain1.com

If I open windows Explorer I can connect to Server1 by its short name
or FQDN. But I cannot hit Data1 by either name, either on the main
server (Server1) or any client PC's or member servers (I have verified
that the change has replicated to other DNS servers on the LAN, too.)

What I get is the message: Windows cannot find "\\Data1" or "Windows
cannot find "\\Data1.Domain1.com"

What am I doing wrong here?

-Fran-

I assume you also receive System error 52 when using net view \\cname. By design, mapping or sharing cname or alias name connections are not supported in Windows network because the Windows performs server name verification. When the computer receives the connection request, it will check the server name verification. If it doesn't match the computer name, you will receive System error 52.


I am not sure why you want to access or map the computer using the different name. You may have 3 options to use the different "names". They are 1) use NetBIOS name; 2) FQDN; 3) IP address.


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<Fran> wrote in message news:(E-Mail Removed)...
I'm trying to set up some DNS aliases (CName records) on a Windows
2000 / 2003 network. On one of the DNS servers I have a server named
Server1 (FQDN: Server1.Domain1.com)

In the DNS consol I create a CName record as follows:

Data1.Domain1.com

This points to Server1.Domain1.com

If I open windows Explorer I can connect to Server1 by its short name
or FQDN. But I cannot hit Data1 by either name, either on the main
server (Server1) or any client PC's or member servers (I have verified
that the change has replicated to other DNS servers on the LAN, too.)

What I get is the message: Windows cannot find "\\Data1" or "Windows
cannot find "\\Data1.Domain1.com"

What am I doing wrong here?

-Fran-

There are many reasons to use CNames (in Windows or other net ops). My
specific use is to create a DNS location that can be used for data:
Physical server is: Server1.Domain1.com

CName: Data1.Domain1.Com --> Server1.Domain1.com

When I get a new server for handling our data uses all I have to do is
change the CName pointer to the new server...I don't have to modify
our clients as they will still point to Data1.

>I assume you also receive System error 52 when using net view \\cname. By design, mapping or sharing cname or alias name connections are not supported in Windows network because the Windows performs server name verification. When the computer receives the connection request, it will check the server name verification. If it doesn't match the computer name, you will receive System error 52.
>
>
>I am not sure why you want to access or map the computer using the different name. You may have 3 options to use the different "names". They are 1) use NetBIOS name; 2) FQDN; 3) IP address.
>
>
>Bob Lin, MS-MVP, MCSE & CNE
>Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
>How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> <Fran> wrote in message news:(E-Mail Removed)...
> I'm trying to set up some DNS aliases (CName records) on a Windows
> 2000 / 2003 network. On one of the DNS servers I have a server named
> Server1 (FQDN: Server1.Domain1.com)
>
> In the DNS consol I create a CName record as follows:
>
> Data1.Domain1.com
>
> This points to Server1.Domain1.com
>
> If I open windows Explorer I can connect to Server1 by its short name
> or FQDN. But I cannot hit Data1 by either name, either on the main
> server (Server1) or any client PC's or member servers (I have verified
> that the change has replicated to other DNS servers on the LAN, too.)
>
> What I get is the message: Windows cannot find "\\Data1" or "Windows
> cannot find "\\Data1.Domain1.com"
>
> What am I doing wrong here?
>
> -Fran-

Try disabling strict name checking on Server1 - see:

http://support.microsoft.com/default...b;en-us;281308

Doug Sherman
MCSE, MCSA, MCP+I, MVP

<Fran> wrote in message news:(E-Mail Removed)...
> I'm trying to set up some DNS aliases (CName records) on a Windows
> 2000 / 2003 network. On one of the DNS servers I have a server named
> Server1 (FQDN: Server1.Domain1.com)
>
> In the DNS consol I create a CName record as follows:
>
> Data1.Domain1.com
>
> This points to Server1.Domain1.com
>
> If I open windows Explorer I can connect to Server1 by its short name
> or FQDN. But I cannot hit Data1 by either name, either on the main
> server (Server1) or any client PC's or member servers (I have verified
> that the change has replicated to other DNS servers on the LAN, too.)
>
> What I get is the message: Windows cannot find "\\Data1" or "Windows
> cannot find "\\Data1.Domain1.com"
>
> What am I doing wrong here?
>
> -Fran-

In this case, I will use logon script or DFS.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<Fran> wrote in message news:(E-Mail Removed)...
There are many reasons to use CNames (in Windows or other net ops). My
specific use is to create a DNS location that can be used for data:
Physical server is: Server1.Domain1.com

CName: Data1.Domain1.Com --> Server1.Domain1.com

When I get a new server for handling our data uses all I have to do is
change the CName pointer to the new server...I don't have to modify
our clients as they will still point to Data1.

>I assume you also receive System error 52 when using net view \\cname. By design, mapping or sharing cname or alias name connections are not supported in Windows network because the Windows performs server name verification. When the computer receives the connection request, it will check the server name verification. If it doesn't match the computer name, you will receive System error 52.
>
>
>I am not sure why you want to access or map the computer using the different name. You may have 3 options to use the different "names". They are 1) use NetBIOS name; 2) FQDN; 3) IP address.
>
>
>Bob Lin, MS-MVP, MCSE & CNE
>Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
>How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> <Fran> wrote in message news:(E-Mail Removed)...
> I'm trying to set up some DNS aliases (CName records) on a Windows
> 2000 / 2003 network. On one of the DNS servers I have a server named
> Server1 (FQDN: Server1.Domain1.com)
>
> In the DNS consol I create a CName record as follows:
>
> Data1.Domain1.com
>
> This points to Server1.Domain1.com
>
> If I open windows Explorer I can connect to Server1 by its short name
> or FQDN. But I cannot hit Data1 by either name, either on the main
> server (Server1) or any client PC's or member servers (I have verified
> that the change has replicated to other DNS servers on the LAN, too.)
>
> What I get is the message: Windows cannot find "\\Data1" or "Windows
> cannot find "\\Data1.Domain1.com"
>
> What am I doing wrong here?
>
> -Fran-

The server is a Windows 2003 server. So, following the instructions I
added the registry key to

HKLM\System\CurrentControlSet\services\LanManServe r\Paramenter
I added: DisableStrictNameChecking (1) <decimal>

I rebooted the server as instructed.

It took a few minutes for something to rattle loose across the network
(even though I forced replication between DNS servers and the alias
showed up on other DNS servers I could not access by alias name for
about 10 minutes.) However, after that this works!

Good call, Doug! This did the trick (I knew MS had to allow for
this...I just wonder why they haven't made this a normal part of the
OS.) It seems silly that you would have to apply a registry hack to
get normal DNS behavior to work in Windows.

Anyway, good call and thanks a ton!


>Try disabling strict name checking on Server1 - see:
>
>http://support.microsoft.com/default...b;en-us;281308
>
>Doug Sherman
>MCSE, MCSA, MCP+I, MVP
>

Go et 'em, Fran!

Doug Sherman
MCSE, MCSA, MCP+I, MVP

<Fran> wrote in message news:(E-Mail Removed)...
> The server is a Windows 2003 server. So, following the instructions I
> added the registry key to
>
> HKLM\System\CurrentControlSet\services\LanManServe r\Paramenter
> I added: DisableStrictNameChecking (1) <decimal>
>
> I rebooted the server as instructed.
>
> It took a few minutes for something to rattle loose across the network
> (even though I forced replication between DNS servers and the alias
> showed up on other DNS servers I could not access by alias name for
> about 10 minutes.) However, after that this works!
>
> Good call, Doug! This did the trick (I knew MS had to allow for
> this...I just wonder why they haven't made this a normal part of the
> OS.) It seems silly that you would have to apply a registry hack to
> get normal DNS behavior to work in Windows.
>
> Anyway, good call and thanks a ton!
>
>
> >Try disabling strict name checking on Server1 - see:
> >
> >http://support.microsoft.com/default...b;en-us;281308
> >
> >Doug Sherman
> >MCSE, MCSA, MCP+I, MVP
> >