multi-homed

Have set up a new 2003 server with one nic. Have assigned it
two IP addresses, one is say 192.168.1.40 and the other is
192.168.1.42. The AD is running in prewindows 2000 mode.

From another desktop it can mount a share using the IP
address, i.e. \\192.168.1.42\d$, but if one tries to use
say \\apple\d$ than you get the following:

You were not connected because a duplicate name exists on
the network. Go to System in Control Panel to change the
computer name and try again.

Tryed using the FQDN with the same result. Tryed using an
lmhost entry with the same result. Any help would be
appreciated. Thank You. LPH!

You need to change one of these IP addresses. You should not have 2 NICs on
the same subnet in a multihomed machine. If the machine is a domain
controller, your problems will escalate rapidly.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"lph" <(E-Mail Removed)> wrote in message
news:2849101c463ab$91205830$(E-Mail Removed)...
> Have set up a new 2003 server with one nic. Have assigned it
> two IP addresses, one is say 192.168.1.40 and the other is
> 192.168.1.42. The AD is running in prewindows 2000 mode.
>
> From another desktop it can mount a share using the IP
> address, i.e. \\192.168.1.42\d$, but if one tries to use
> say \\apple\d$ than you get the following:
>
> You were not connected because a duplicate name exists on
> the network. Go to System in Control Panel to change the
> computer name and try again.
>
> Tryed using the FQDN with the same result. Tryed using an
> lmhost entry with the same result. Any help would be
> appreciated. Thank You. LPH!

Sorry, I now see that you said one NIC. This article outlines some of the
considerations when assigning multiple IP addresses to a single adapter.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> You need to change one of these IP addresses. You should not have 2 NICs
on
> the same subnet in a multihomed machine. If the machine is a domain
> controller, your problems will escalate rapidly.
>
> Doug Sherman
> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
> "lph" <(E-Mail Removed)> wrote in message
> news:2849101c463ab$91205830$(E-Mail Removed)...
> > Have set up a new 2003 server with one nic. Have assigned it
> > two IP addresses, one is say 192.168.1.40 and the other is
> > 192.168.1.42. The AD is running in prewindows 2000 mode.
> >
> > From another desktop it can mount a share using the IP
> > address, i.e. \\192.168.1.42\d$, but if one tries to use
> > say \\apple\d$ than you get the following:
> >
> > You were not connected because a duplicate name exists on
> > the network. Go to System in Control Panel to change the
> > computer name and try again.
> >
> > Tryed using the FQDN with the same result. Tryed using an
> > lmhost entry with the same result. Any help would be
> > appreciated. Thank You. LPH!
>
>

http://www.microsoft.com/resources/d...c_tcp_qpzj.asp

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Sorry, I now see that you said one NIC. This article outlines some of the
> considerations when assigning multiple IP addresses to a single adapter.
>
> Doug Sherman
> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > You need to change one of these IP addresses. You should not have 2
NICs
> on
> > the same subnet in a multihomed machine. If the machine is a domain
> > controller, your problems will escalate rapidly.
> >
> > Doug Sherman
> > MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> > "lph" <(E-Mail Removed)> wrote in message
> > news:2849101c463ab$91205830$(E-Mail Removed)...
> > > Have set up a new 2003 server with one nic. Have assigned it
> > > two IP addresses, one is say 192.168.1.40 and the other is
> > > 192.168.1.42. The AD is running in prewindows 2000 mode.
> > >
> > > From another desktop it can mount a share using the IP
> > > address, i.e. \\192.168.1.42\d$, but if one tries to use
> > > say \\apple\d$ than you get the following:
> > >
> > > You were not connected because a duplicate name exists on
> > > the network. Go to System in Control Panel to change the
> > > computer name and try again.
> > >
> > > Tryed using the FQDN with the same result. Tryed using an
> > > lmhost entry with the same result. Any help would be
> > > appreciated. Thank You. LPH!
> >
> >
>
>

I suppose assigning two different IP addresses from the same subnet to the
same adapter would effectively be the same as having two nics on the same
subnet. Question is, why assign an adapter two different IP addresses on the
same subnet?

One common reason is if it is a webserver. You need a separate IP# per each
website unless you want to use Host Headers or varying ports to designate
them. Other than that you are right,...there are very few reason for doing
it.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Dodo" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> I suppose assigning two different IP addresses from the same subnet to the
> same adapter would effectively be the same as having two nics on the same
> subnet. Question is, why assign an adapter two different IP addresses on
the
> same subnet?
>
>

About 75% of the time (IMO) it is due to people misunderstanding their needs
and choosing an improper method to accomplish something.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Dodo" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> I suppose assigning two different IP addresses from the same subnet to the
> same adapter would effectively be the same as having two nics on the same
> subnet. Question is, why assign an adapter two different IP addresses on
the
> same subnet?
>
>

Doug:

I read the article, but the question still remains, how
can I use a FQDN without getting the error message?

Thanks.

LPH


>-----Original Message-----
>http://www.microsoft.com/resources/d...c_tcp_qpzj.asp
>
>Doug Sherman
>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
>"Doug Sherman [MVP]" <(E-Mail Removed)>
wrote in message
>news:%(E-Mail Removed)...
>> Sorry, I now see that you said one NIC. This article
outlines some of the
>> considerations when assigning multiple IP addresses to a
single adapter.
>>
>> Doug Sherman
>> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>>
>> "Doug Sherman [MVP]" <(E-Mail Removed)>
wrote in message
>> news:(E-Mail Removed)...
>> > You need to change one of these IP addresses. You
should not have 2
>NICs
>> on
>> > the same subnet in a multihomed machine. If the
machine is a domain
>> > controller, your problems will escalate rapidly.
>> >
>> > Doug Sherman
>> > MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>> >
>> > "lph" <(E-Mail Removed)> wrote in
message
>> > news:2849101c463ab$91205830$(E-Mail Removed)...
>> > > Have set up a new 2003 server with one nic. Have
assigned it
>> > > two IP addresses, one is say 192.168.1.40 and the
other is
>> > > 192.168.1.42. The AD is running in prewindows 2000
mode.
>> > >
>> > > From another desktop it can mount a share using the IP
>> > > address, i.e. \\192.168.1.42\d$, but if one tries to use
>> > > say \\apple\d$ than you get the following:
>> > >
>> > > You were not connected because a duplicate name
exists on
>> > > the network. Go to System in Control Panel to
change the
>> > > computer name and try again.
>> > >
>> > > Tryed using the FQDN with the same result. Tryed
using an
>> > > lmhost entry with the same result. Any help would be
>> > > appreciated. Thank You. LPH!
>> >
>> >
>>
>>
>
>
>.
>