Same server with two different names

[Guest]

Hello,

I have a file server with the NETBIOS name XPTO and FQDN xpto.ad.teste.com .

Through UNC path I can browse the shared files and folders at XPTO
(\\XPTO\...).

Now I need to access the same server trough UNC but using the name XPTI
(\\XPTI\...).

What I did:
- In the DNS domain I created a new record: xpti.ad.teste.com with the same
IP address
- In the WINS I created a new record: XPTI (Workstation [00h] and
Server[20h]) with the same IP address

I can ping XPTI successfully, but I can't browse the shared files and
folders through UNC path.

What's the problem?

Thanks
Dudu

 

[Robert L [MS-MVP]]

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 “nameâ€. 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
Hello,

I have a file server with the NETBIOS name XPTO and FQDN xpto.ad.teste.com .

Through UNC path I can browse the shared files and folders at XPTO
(\\XPTO\...).

Now I need to access the same server trough UNC but using the name XPTI
(\\XPTI\...).

What I did:
- In the DNS domain I created a new record: xpti.ad.teste.com with the same
IP address
- In the WINS I created a new record: XPTI (Workstation [00h] and
Server[20h]) with the same IP address

I can ping XPTI successfully, but I can't browse the shared files and
folders through UNC path.

What's the problem?

Thanks
Dudu

 

[Phillip Windell]

Anytime you think you have to reference a machine by two different
names,...is when you need to go back and rethink the whole situation that
got you to that point in the first place.

 

[Fran]

I would use an Alias (CNAME) instead. Since you already have a valid
DNS record to XPTO you can alias that same server as XTPI

e.g. in DNS you have XTPO.domain.com
Create an alias (CNAME) record as follows:

XTPI.domain.com
points to
XTPO.domain.com
(the alias/CNAME dialog in DNS is pretty straight forward.)

Now, Windows does not natively support alias recognition (don't ask me
why...doesn't make ANY sense at all. But MS did issue a patch for this
as someone already pointed out to me in a previous post.) Do the
following on the TARGET server (assuming you're running Windows 2000
Server with SP3 or later or Windows 2003)

1) Open Regedit, navigate to
HKLM\System\CurrentControlSet\services\LanManServer\Paramenter
2) From the EDIT menu click NEW then DWord Value.
a) Name this: DisableStrictNameChecking
b) value is: 1 <decimal>

Close RegEdit and restart the server.

This must be done on the TARGET server (in your case, XTPO)

Although other posters are correct in that Windows does not natively
support Aliases this fix, by Microsoft, fixes that mistake.

Note that this will take a few minutes after booting (and DNS
replication) to work. In my testing (across domains) I had to use the
FQDN once on the neighboring lan and then I could just use the short
name (XTPI) instead of the FQDN (XTPI.Domain.com)

Hope this solves the problem.

-Fran-

 

[Guest]

Thanks for all the replies, but the solution is this one:

http://support.microsoft.com/?id=281308

I need to reference a machine by two different names only because old
application compatibility reasons.