Duplicate Name Exists on Network

Over the weekend we had some of our guys rebuild one of
our NT 4.0 BDCs (NT domain) as a Win2003 member server in
our new AD domain. It was also renamed in the process.

They cnamed the old hostname to the newhostname (e.g.,
A.NTdomain.com ---> B.ADdomain.com) due to having some
apps hard coded with the old server name.

I came in this morning and found that the apps that had
the UNC name hard codded for the old server werent
working. The error they are receiving is:

"You were not connected because a duplicate name exists
on the network."

These are apps in the NT domain.

We are running WINS and made sure WINS was cleared out.
I also removed the old server account from the NT
domain.

I have flushed the netbios cache on the local boxes and
the wins servers. I have double checked the server IP
properties to make sure the settings were correct.

I ran nbtstat -a <server> name and received host not
found. I ran "net view <server>" and received the
same "duplicate name exists.." error.

At this point, we should be receiving host not found if
anything. I am at a loss now.

The desired result is to have this "duplicate name"
problem fixed so that both names resolve to the new
server. The thought is that if we remove the old server
entry from WINS (which has been done), wins would then
forward the name on to DNS and dns would resolve the name-
-hence the cname.

However, I am all out of ideas on how to fix the
duplicate name issue.

Any suggestions would be appreciated

Thanks
RS


Any suggestions would be appreciated.

Have reverse look up zone also? Do those applications also perform
reverse look up for the hostname?

"RS" <(E-Mail Removed)> wrote in message
news:083d01c3c33b$0e514600$(E-Mail Removed)...
> Over the weekend we had some of our guys rebuild one of
> our NT 4.0 BDCs (NT domain) as a Win2003 member server in
> our new AD domain. It was also renamed in the process.
>
> They cnamed the old hostname to the newhostname (e.g.,
> A.NTdomain.com ---> B.ADdomain.com) due to having some
> apps hard coded with the old server name.
>
> I came in this morning and found that the apps that had
> the UNC name hard codded for the old server werent
> working. The error they are receiving is:
>
> "You were not connected because a duplicate name exists
> on the network."
>
> These are apps in the NT domain.
>
> We are running WINS and made sure WINS was cleared out.
> I also removed the old server account from the NT
> domain.
>
> I have flushed the netbios cache on the local boxes and
> the wins servers. I have double checked the server IP
> properties to make sure the settings were correct.
>
> I ran nbtstat -a <server> name and received host not
> found. I ran "net view <server>" and received the
> same "duplicate name exists.." error.
>
> At this point, we should be receiving host not found if
> anything. I am at a loss now.
>
> The desired result is to have this "duplicate name"
> problem fixed so that both names resolve to the new
> server. The thought is that if we remove the old server
> entry from WINS (which has been done), wins would then
> forward the name on to DNS and dns would resolve the name-
> -hence the cname.
>
> However, I am all out of ideas on how to fix the
> duplicate name issue.
>
> Any suggestions would be appreciated
>
> Thanks
> RS
>
>
> Any suggestions would be appreciated.
>
>
>
>

Thanks for the reply.

They do not. However, I checked DNS just to be sure and
its all clear.


>-----Original Message-----
>Have reverse look up zone also? Do those applications
also perform
>reverse look up for the hostname?
>
>"RS" <(E-Mail Removed)> wrote in
message
>news:083d01c3c33b$0e514600$(E-Mail Removed)...
>> Over the weekend we had some of our guys rebuild one of
>> our NT 4.0 BDCs (NT domain) as a Win2003 member server
in
>> our new AD domain. It was also renamed in the process.
>>
>> They cnamed the old hostname to the newhostname (e.g.,
>> A.NTdomain.com ---> B.ADdomain.com) due to having some
>> apps hard coded with the old server name.
>>
>> I came in this morning and found that the apps that had
>> the UNC name hard codded for the old server werent
>> working. The error they are receiving is:
>>
>> "You were not connected because a duplicate name exists
>> on the network."
>>
>> These are apps in the NT domain.
>>
>> We are running WINS and made sure WINS was cleared out.
>> I also removed the old server account from the NT
>> domain.
>>
>> I have flushed the netbios cache on the local boxes and
>> the wins servers. I have double checked the server IP
>> properties to make sure the settings were correct.
>>
>> I ran nbtstat -a <server> name and received host not
>> found. I ran "net view <server>" and received the
>> same "duplicate name exists.." error.
>>
>> At this point, we should be receiving host not found if
>> anything. I am at a loss now.
>>
>> The desired result is to have this "duplicate name"
>> problem fixed so that both names resolve to the new
>> server. The thought is that if we remove the old
server
>> entry from WINS (which has been done), wins would then
>> forward the name on to DNS and dns would resolve the
name-
>> -hence the cname.
>>
>> However, I am all out of ideas on how to fix the
>> duplicate name issue.
>>
>> Any suggestions would be appreciated
>>
>> Thanks
>> RS
>>
>>
>> Any suggestions would be appreciated.
>>
>>
>>
>>
>
>
>.
>

Did you guys keep the same IP address as the old NT
server??? I had a similar problem with 2003. I had NT
server that I have replaced with (new box) 2003 and I have
kept same name and IP address and I was getting the same
message. The way I fixed this was by changing an IP and
name used to something else and then trying connection via
UNC and pinging it. I did hafta wait about 15 minutes for
it to "replicate" and advertise itself on network with
changed name. Then I had changed the server 2003 back to
the old name and old IP and it worked, I had to come in on
Saturday to do this but it finaly worked after fussing
around with it for about a week. Try it and let us know.
I think that maybe a Microsoft glitch.... Also some
printers like hp4050n will not connect at all to a 2003
server unless you update a Firmware version on printer.
Good Luck.

Intetresting...

I will give it a try. Thanks!
>-----Original Message-----
>Did you guys keep the same IP address as the old NT
>server??? I had a similar problem with 2003. I had NT
>server that I have replaced with (new box) 2003 and I
have
>kept same name and IP address and I was getting the same
>message. The way I fixed this was by changing an IP and
>name used to something else and then trying connection
via
>UNC and pinging it. I did hafta wait about 15 minutes
for
>it to "replicate" and advertise itself on network with
>changed name. Then I had changed the server 2003 back to
>the old name and old IP and it worked, I had to come in
on
>Saturday to do this but it finaly worked after fussing
>around with it for about a week. Try it and let us
know.
>I think that maybe a Microsoft glitch.... Also some
>printers like hp4050n will not connect at all to a 2003
>server unless you update a Firmware version on printer.
>Good Luck.
>.
>

NETBIOS only allows for a single name for a system.
You can't use DNS cnames, lmhosts or anything like that to
work around this as the limitation exists above IP.

There is an unsupported (but widely-known) registry hack
you can use to assign multiple NetBIOS names to a server:
Browse regedt32 on the server to

HKLM \ System \ CurrentControlSet \ Services \ LanManServer \ Parameters

and create a REG_MUL:TI_SZ entry called OptionalNames and put in the list
of all the alias names you want to assign to the server. Then reboot.

Again, this is entirely unsupported by MS and I've never tried it on Win2K3 so
it may not work at all. And if you are running WINS you may need to
make manual entries for some of these names also, I'm not sure -- check the WINS
db after the server boots and/or use nbtstat to check.

Steve Duff, MCSE
Ergodic Systems, Inc.

"RS" <(E-Mail Removed)> wrote in message news:083d01c3c33b$0e514600$(E-Mail Removed)...
> Over the weekend we had some of our guys rebuild one of
> our NT 4.0 BDCs (NT domain) as a Win2003 member server in
> our new AD domain. It was also renamed in the process.
>
> They cnamed the old hostname to the newhostname (e.g.,
> A.NTdomain.com ---> B.ADdomain.com) due to having some
> apps hard coded with the old server name.
>
> I came in this morning and found that the apps that had
> the UNC name hard codded for the old server werent
> working. The error they are receiving is:
>
> "You were not connected because a duplicate name exists
> on the network."
>
> These are apps in the NT domain.
>
> We are running WINS and made sure WINS was cleared out.
> I also removed the old server account from the NT
> domain.
>
> I have flushed the netbios cache on the local boxes and
> the wins servers. I have double checked the server IP
> properties to make sure the settings were correct.
>
> I ran nbtstat -a <server> name and received host not
> found. I ran "net view <server>" and received the
> same "duplicate name exists.." error.
>
> At this point, we should be receiving host not found if
> anything. I am at a loss now.
>
> The desired result is to have this "duplicate name"
> problem fixed so that both names resolve to the new
> server. The thought is that if we remove the old server
> entry from WINS (which has been done), wins would then
> forward the name on to DNS and dns would resolve the name-
> -hence the cname.
>
> However, I am all out of ideas on how to fix the
> duplicate name issue.
>
> Any suggestions would be appreciated
>
> Thanks
> RS
>
>
> Any suggestions would be appreciated.
>
>
>
>

Well, we followed the suggestion below and unfortunately,
it did not resolve the issue.

I appreciate the suggestions thus far and hope they keep
coming.

Thanks
RS


>-----Original Message-----
>Did you guys keep the same IP address as the old NT
>server??? I had a similar problem with 2003. I had NT
>server that I have replaced with (new box) 2003 and I
have
>kept same name and IP address and I was getting the same
>message. The way I fixed this was by changing an IP and
>name used to something else and then trying connection
via
>UNC and pinging it. I did hafta wait about 15 minutes
for
>it to "replicate" and advertise itself on network with
>changed name. Then I had changed the server 2003 back to
>the old name and old IP and it worked, I had to come in
on
>Saturday to do this but it finaly worked after fussing
>around with it for about a week. Try it and let us
know.
>I think that maybe a Microsoft glitch.... Also some
>printers like hp4050n will not connect at all to a 2003
>server unless you update a Firmware version on printer.
>Good Luck.
>.
>

I figured I should post an update as to what we have done
thus far:

We played with this a couple of different ways, but
nothing was successful except renaming the server back to
the old name. This isn't an option, so we had to set it
back. BTW, we also played with re-IP'ing and using a
static WINS entry instead of a DNS cname, not to mention
rebooting both the name servers.

We changed the IP as part of the procedure above and we
are leaving it up with the new IP. Hopefully, things
will clear up this way.

Very strange issue. We have never run into this before.


>-----Original Message-----
>Did you guys keep the same IP address as the old NT
>server??? I had a similar problem with 2003. I had NT
>server that I have replaced with (new box) 2003 and I
have
>kept same name and IP address and I was getting the same
>message. The way I fixed this was by changing an IP and
>name used to something else and then trying connection
via
>UNC and pinging it. I did hafta wait about 15 minutes
for
>it to "replicate" and advertise itself on network with
>changed name. Then I had changed the server 2003 back to
>the old name and old IP and it worked, I had to come in
on
>Saturday to do this but it finaly worked after fussing
>around with it for about a week. Try it and let us
know.
>I think that maybe a Microsoft glitch.... Also some
>printers like hp4050n will not connect at all to a 2003
>server unless you update a Firmware version on printer.
>Good Luck.
>.
>

Thanks Steve.

We will try this hack and see if it resolves our problem.
>-----Original Message-----
>NETBIOS only allows for a single name for a system.
>You can't use DNS cnames, lmhosts or anything like that
to
>work around this as the limitation exists above IP.
>
>There is an unsupported (but widely-known) registry hack
>you can use to assign multiple NetBIOS names to a server:
>Browse regedt32 on the server to
>
>HKLM \ System \ CurrentControlSet \ Services \
LanManServer \ Parameters
>
>and create a REG_MUL:TI_SZ entry called OptionalNames
and put in the list
>of all the alias names you want to assign to the server.
Then reboot.
>
>Again, this is entirely unsupported by MS and I've never
tried it on Win2K3 so
>it may not work at all. And if you are running WINS you
may need to
>make manual entries for some of these names also, I'm
not sure -- check the WINS
>db after the server boots and/or use nbtstat to check.
>
>Steve Duff, MCSE
>Ergodic Systems, Inc.
>
>"RS" <(E-Mail Removed)> wrote in
message news:083d01c3c33b$0e514600$(E-Mail Removed)...
>> Over the weekend we had some of our guys rebuild one of
>> our NT 4.0 BDCs (NT domain) as a Win2003 member server
in
>> our new AD domain. It was also renamed in the process.
>>
>> They cnamed the old hostname to the newhostname (e.g.,
>> A.NTdomain.com ---> B.ADdomain.com) due to having some
>> apps hard coded with the old server name.
>>
>> I came in this morning and found that the apps that had
>> the UNC name hard codded for the old server werent
>> working. The error they are receiving is:
>>
>> "You were not connected because a duplicate name exists
>> on the network."
>>
>> These are apps in the NT domain.
>>
>> We are running WINS and made sure WINS was cleared out.
>> I also removed the old server account from the NT
>> domain.
>>
>> I have flushed the netbios cache on the local boxes and
>> the wins servers. I have double checked the server IP
>> properties to make sure the settings were correct.
>>
>> I ran nbtstat -a <server> name and received host not
>> found. I ran "net view <server>" and received the
>> same "duplicate name exists.." error.
>>
>> At this point, we should be receiving host not found if
>> anything. I am at a loss now.
>>
>> The desired result is to have this "duplicate name"
>> problem fixed so that both names resolve to the new
>> server. The thought is that if we remove the old
server
>> entry from WINS (which has been done), wins would then
>> forward the name on to DNS and dns would resolve the
name-
>> -hence the cname.
>>
>> However, I am all out of ideas on how to fix the
>> duplicate name issue.
>>
>> Any suggestions would be appreciated
>>
>> Thanks
>> RS
>>
>>
>> Any suggestions would be appreciated.
>>
>>
>>
>>
>
>
>.
>