Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Dns Problem 1

Status
Not open for further replies.
Jun 26, 2002
58
US
Hello all,

I have a host record on my Microsoft Active Directory dns servers that points xxxx.yyyy.com to 1.1.1.1 . We then created a alias record pointing zzzz.yyyy.com to 1.1.1.1 .

When we try and access a share on the machine via the host record everything works.
(e.g. \\xxxx.yyyy.com\c$ )

When we try and access a share on the macine via the alias it gives an error "Duplicate computer name on the network"
(e.g. \\zzzz.yyyy.com\c$ )

We have verified no machine named zzzz is on the network, and we have no duplicate records on the wins or dns.

The ping of zzzz.yyyy.com resolves correctly to xxxx.yyyy.com and comes back with the right IP address.

We also use WINS on our network until the windows 2000 migration is complete. Both NT4.0 clients and AD clients point to the same wins and same DNS.

Anyone have a clue what is wrong with this?

thanks!

mm
 
Your confusing DNS with Lan Manager. Adding an entry to the DNS won't make the \\NEWNAME\<share> work. You need to add that in your LMHOSTS file.




&quot;In space, nobody can hear you click...&quot;
 
yes it will. You can access shares via FQDN's. We use them all the time, just having a problem with this one.

Adding a enter to the LMHOSTS file would require a modification to 400+ machines. Plus it would not identify nor fix the underlying problem.

Note my original post that \\xxxx.yyyy.com\c$ works.

Thanks!

mm
 
mm,
Change your alias entry from pointing from 1.1.1.1 to pointing to xxxx.yyyy.com.
 
No it won't, unless there is something that can trick it in the DNS.


xxxx.yyyy.com will work cause it's in the WINS and is resolved for your Lan Manager, but not zzzz.yyyy.com. Adding zzzz.yyyy.com to the DNS will give you the capability of using TCP/IP functions, such as PING. In order for a share to work, Fully Qualified or not, the WINS resolves it and you can only have one name per machine for the LAN manager. That is why you get a duplicate name, cause when you try to attach to the drive, your system will lookup the IP in the WINS and find it already exists under XXXX.YYYY.COM. Duplicate computer name.





&quot;In space, nobody can hear you click...&quot;
 
I think I see what you are doing. You want to have a server be known to the network as TWO names.

I believe that you will have to make the registry entry on your server to get this to work:


0062 » Give your machine a Netbios alias in Windows NT.




If you have an machine name that is invalid for SQL Server, Exchange, or just want to be cute, you can change it in Control Panel / Networks, but that could be a lot of work.

Create an alias instead, by editing:

HKEY_Local_Machine\System\CurrentControlSet\Services\LanmanServer\Parameters

Add Value: OptionalNames REG_SZ String: &quot;Alias&quot;

If you make it a type REG_MULTI_SZ, you can add multiple aliases.



-hope this helps..

Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
cool...thanks for the post...must be the newest way to fix an old problem :)

Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
Joseph,

Thanks again! Your solution will work as well! Thanks for your help!

mm
 
I just tried it too and it works... That will save me a few headaches in the futur!




&quot;In space, nobody can hear you click...&quot;
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top