Computer names and network shares with DNS


N

Natan Vivo

I would like to know if there is any way to use DNS to resolve machine
names and access windows network shares through them. Our office network
is Windows 2000/XP only.

We use Linux+BIND for DNS servers (because it is the same external DNS)
and we realy don't want to use Windows 2003 DNS Server (don't ask).

As we are changing lots of things here, we have some services we would
like to have more flexibility about where they are.

Now, if we have a server named "server1" in our domain, we can access a
share through "\\server1.ourdomain.com\share". But if I create a CNAME
or another A record to the same computer, it doesn't work.

I would like to make "\\files.ourdomain.com\public\" or
"\\sales.ourdomain.com\" point to server1.ourdomain.com just like we do
with real domain names.

I don't know if windows still uses netbios to resolve domain names,
because an "nslookup files.ourdomain.com" resolves to the right
computer, but "\\files.ourdomain.com" gives me "computer not found"
error. So if anyone can clarify me on this, i would be thankful.
 
Ad

Advertisements

A

Ace Fekay [MVP]

In
Natan Vivo said:
I would like to know if there is any way to use DNS to resolve machine
names and access windows network shares through them. Our office
network is Windows 2000/XP only.

We use Linux+BIND for DNS servers (because it is the same external
DNS) and we realy don't want to use Windows 2003 DNS Server (don't
ask).
As we are changing lots of things here, we have some services we would
like to have more flexibility about where they are.

Now, if we have a server named "server1" in our domain, we can access
a share through "\\server1.ourdomain.com\share". But if I create a
CNAME or another A record to the same computer, it doesn't work.

I would like to make "\\files.ourdomain.com\public\" or
"\\sales.ourdomain.com\" point to server1.ourdomain.com just like we
do with real domain names.

I don't know if windows still uses netbios to resolve domain names,
because an "nslookup files.ourdomain.com" resolves to the right
computer, but "\\files.ourdomain.com" gives me "computer not found"
error. So if anyone can clarify me on this, i would be thankful.

You can adjust the registry to *force* it to:
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/default.aspx?scid=kb;en-us;281308

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Microsot Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
 
J

Jorge_de_Almeida_Pinto

I would like to know if there is any way to use DNS to resolve
machine
names and access windows network shares through them. Our
office network
is Windows 2000/XP only.

We use Linux+BIND for DNS servers (because it is the same
external DNS)
and we realy don't want to use Windows 2003 DNS Server (don't
ask).

As we are changing lots of things here, we have some services
we would
like to have more flexibility about where they are.

Now, if we have a server named "server1" in our domain, we can
access a
share through "\server1.ourdomain.comshare". But if I create
a CNAME
or another A record to the same computer, it doesn't work.

I would like to make "\files.ourdomain.compublic" or
"\sales.ourdomain.com" point to server1.ourdomain.com just
like we do
with real domain names.

I don't know if windows still uses netbios to resolve domain
names,
because an "nslookup files.ourdomain.com" resolves to the
right
computer, but "\files.ourdomain.com" gives me "computer not
found"
error. So if anyone can clarify me on this, i would be
thankful.

if I remember correctly and you are talking about Windows 2003 servers
you could use NETDOM to assign an additional computername for the
server. Doing it like that will also register the new name as a
service principal name on the computer account of the server

netdom computername /add etc.
 
Ad

Advertisements

J

Jorge_de_Almeida_Pinto

Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top