razor192
asked on
duplicate name exists on network??
haveing a little name resolution issue on a small network.. no domain controllers.
Migrating contents of windows 2k (Atlas) file server to an existing 2k3 (titan) file server. Both machine have existed on network for some time now..
I have a local DNS entry for Titan ( A Record 192.168.1.100)
copied data from Atlas to Titan, recreated the shares, permissions, etc..
there are some apps in the office that point to \\atlas\share for data so I wanted to keep the "atlas" name around and just point it to the new IP where the shares now exist...
Created and A record for Atlas that points to the IP of Titan (192.168.1.100)
turned the old 2k server off.
Now when I try to map a drive to \\atlas\share or "run" \\atlas\share i get and error that says "A duplicate name exists on the network"
I can ping both Atlas and Titan fine. they resolve to the same IP. i can map to teh new shares via IP just fine. \\192.168.1.100\share .....
any thoughts??
Migrating contents of windows 2k (Atlas) file server to an existing 2k3 (titan) file server. Both machine have existed on network for some time now..
I have a local DNS entry for Titan ( A Record 192.168.1.100)
copied data from Atlas to Titan, recreated the shares, permissions, etc..
there are some apps in the office that point to \\atlas\share for data so I wanted to keep the "atlas" name around and just point it to the new IP where the shares now exist...
Created and A record for Atlas that points to the IP of Titan (192.168.1.100)
turned the old 2k server off.
Now when I try to map a drive to \\atlas\share or "run" \\atlas\share i get and error that says "A duplicate name exists on the network"
I can ping both Atlas and Titan fine. they resolve to the same IP. i can map to teh new shares via IP just fine. \\192.168.1.100\share .....
any thoughts??
scrathcyboy
You cannot have diplicate names on a windows network. Name the computer one name or the other, and dont have 2 names for the one computer. It will give you trouble down the road. Also, stop any servers that think the old system is running, reboot them. Windows name service file sharing remembers what it should forget, and forgets what it should remember. It is a difficult ADHD child, and needs to be treated that way. Do NOT confuse this OS, it will bite you in the butt if you do. One name per computer, NO duplicate names.
ASKER
so am i understanding you correctly.. you say it is not a good idea to have a server refered to by 2 different DNS names?? ie and A record for Atlas that points to 192.168.1.100 and an A record for Titan that also points to 192.168.1.100 ??
The above post is incorrect. There is absolutely no reason why an IP shouldn't be resolved by 2 dns names, although I'd use a CNAME instead of 2 A records. The computer name is quite different and should obviously be individual, and as you are not running a domain it may or may not have the same name as the DNS record, it doesn't really matter from a functionality point of view. If the old server was switched off it's probably just cached information somewhere. If you run an ipconfig /flushdns or reboot you'll probably find it's gone.
There might also be some remnants in the wins database, so also remove the old entries from there. hosts files on every PC can also have some old entries.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"...turned the old 2k server off"
Now THAT'S the problem.
Solution would be as simple as turning "old 2k" server back ON , UNSHARE folders on Atlas and THEN power off the server.
"...There are some apps in the office that point to \\atlas\share for data so I wanted to keep the "atlas" name around ..."
Now substitute computer name "Atlas" with the correct name "Titan" and restart your network.
Next time your network is up and running browser master will ( hopefully) broadcats all available resources on network correctly ( old and nonexisting entries will be disregard and new shared folders ( on Titan) should appear in the list of shared resources on your network) .
good luck
nedvis
Now THAT'S the problem.
Solution would be as simple as turning "old 2k" server back ON , UNSHARE folders on Atlas and THEN power off the server.
"...There are some apps in the office that point to \\atlas\share for data so I wanted to keep the "atlas" name around ..."
Now substitute computer name "Atlas" with the correct name "Titan" and restart your network.
Next time your network is up and running browser master will ( hopefully) broadcats all available resources on network correctly ( old and nonexisting entries will be disregard and new shared folders ( on Titan) should appear in the list of shared resources on your network) .
good luck
nedvis
You still cannot have two machines with the same IP Address, but you can have one machine with many IP Addresses.
And names should not matter because resolution should be by IP Address, not by name. Now, if you have two differenet machines with the same name on the same domain, yes, it will break, but that is not a "collision" that is a divergence, the opposite of a "collision." The routing would fork in trying to find the correct path, unless and except it knew the IP Address first, in which case, the name can be disregarded. But this is not usually the case. As with most internet traffic, access is requrested first via name, so that this suggests that names must be unique. But that is between two or more machines. It does get kind of tricky because even with unique IP Addreses some programs, like browsers, are name dependent and do not pre-empt names for numbers. The result is that you get two reverse records for the same name, you diverge, and you don't know which one to select, which one is the "real" name you were looking for.
It's still easier to give Titan another IP Address with the associated Atlas name and there should be no collision nor divergence. It works just like a CNAME and Windows under each adapter has a provision for multiple IP Addresses, the hard part is in associating a name with that IP Address, since Windows makes little or no provision for it with all of its numerous "wizards."
The wizards, apparently, are not so witty as to be considered true witans.
And names should not matter because resolution should be by IP Address, not by name. Now, if you have two differenet machines with the same name on the same domain, yes, it will break, but that is not a "collision" that is a divergence, the opposite of a "collision." The routing would fork in trying to find the correct path, unless and except it knew the IP Address first, in which case, the name can be disregarded. But this is not usually the case. As with most internet traffic, access is requrested first via name, so that this suggests that names must be unique. But that is between two or more machines. It does get kind of tricky because even with unique IP Addreses some programs, like browsers, are name dependent and do not pre-empt names for numbers. The result is that you get two reverse records for the same name, you diverge, and you don't know which one to select, which one is the "real" name you were looking for.
It's still easier to give Titan another IP Address with the associated Atlas name and there should be no collision nor divergence. It works just like a CNAME and Windows under each adapter has a provision for multiple IP Addresses, the hard part is in associating a name with that IP Address, since Windows makes little or no provision for it with all of its numerous "wizards."
The wizards, apparently, are not so witty as to be considered true witans.
ASKER
GinEric..
http://support.microsoft.com/default.aspx?scid=kb;en-us;281308 worked like a charm..
I had initally tried to use a CNAME to get Atlas to resolve to titan.blah.com but i could not map drives via the cnae refrence. then I tried the 2 A records .. and ran into the duplicate name error.
thanks all. prob fixed.
http://support.microsoft.com/default.aspx?scid=kb;en-us;281308 worked like a charm..
I had initally tried to use a CNAME to get Atlas to resolve to titan.blah.com but i could not map drives via the cnae refrence. then I tried the 2 A records .. and ran into the duplicate name error.
thanks all. prob fixed.