duplicate name on network when switching wireless to wired network

we have the following problem.
1. user laptop is connected to the wired network, but wireless also enabled
and connected to corporate wifi.
2. user gets up and disconnects from wired network, but is still connected
to wireless network.
3. user returns to desk, plugs back into wired network (while still
connected to wireless network) and gets 'duplicate name on the network found'
error.

the error only appears once AND only happens with Windows XP (all at SP3).
This does not happen with Vista so my thought is that there is something
different in the network stack that allows fast switching between wired and
wireless. question: is there a setting that can be changed to all this to
occur? note IP of wireless and wired networks are different ranges.

John

Never ever ever ever connect to the same network with two adapters at the
same time. Either use the wired always,..or use the wireless always,...make
a choice, stay with it.

Or at least at a minimum only use one at a time, but you may have periodical
problems,...it is just the way it is. The same machine simply cannot be
"known" by two IP#s at the same time.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------



"John" <> wrote in message
news:0439F1D4-B2C9-42DA-B54F-...
> we have the following problem.
> 1. user laptop is connected to the wired network, but wireless also
> enabled
> and connected to corporate wifi.
> 2. user gets up and disconnects from wired network, but is still connected
> to wireless network.
> 3. user returns to desk, plugs back into wired network (while still
> connected to wireless network) and gets 'duplicate name on the network
> found'
> error.
>
> the error only appears once AND only happens with Windows XP (all at SP3).
> This does not happen with Vista so my thought is that there is something
> different in the network stack that allows fast switching between wired
> and
> wireless. question: is there a setting that can be changed to all this to
> occur? note IP of wireless and wired networks are different ranges.

Phillip Windell

Phillip,

I generally agree with you, but Vista and Mac clients do the same things on
our network and do not get this message which leads me to believe that MS
addressed this issue with the network stack in Vista and that there may (or
may not be) a way to control this behavior in XP. My users are not that
savvy, even with some education. they see the company wired and wireless
network as seamless and therefore think that this should just work.


"Phillip Windell" wrote:

> Never ever ever ever connect to the same network with two adapters at the
> same time. Either use the wired always,..or use the wireless always,...make
> a choice, stay with it.
>
> Or at least at a minimum only use one at a time, but you may have periodical
> problems,...it is just the way it is. The same machine simply cannot be
> "known" by two IP#s at the same time.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>
> "John" <> wrote in message
> news:0439F1D4-B2C9-42DA-B54F-...
> > we have the following problem.
> > 1. user laptop is connected to the wired network, but wireless also
> > enabled
> > and connected to corporate wifi.
> > 2. user gets up and disconnects from wired network, but is still connected
> > to wireless network.
> > 3. user returns to desk, plugs back into wired network (while still
> > connected to wireless network) and gets 'duplicate name on the network
> > found'
> > error.
> >
> > the error only appears once AND only happens with Windows XP (all at SP3).
> > This does not happen with Vista so my thought is that there is something
> > different in the network stack that allows fast switching between wired
> > and
> > wireless. question: is there a setting that can be changed to all this to
> > occur? note IP of wireless and wired networks are different ranges.
>
>
>

John

Hi
May be that configuring the Metrics on the cards would solve the issue.
http://www.ezlan.net/metrics.html
Jack (MS, MVP-Networking)

"John" <> wrote in message
news:0439F1D4-B2C9-42DA-B54F-...
> we have the following problem.
> 1. user laptop is connected to the wired network, but wireless also
> enabled
> and connected to corporate wifi.
> 2. user gets up and disconnects from wired network, but is still connected
> to wireless network.
> 3. user returns to desk, plugs back into wired network (while still
> connected to wireless network) and gets 'duplicate name on the network
> found'
> error.
>
> the error only appears once AND only happens with Windows XP (all at SP3).
> This does not happen with Vista so my thought is that there is something
> different in the network stack that allows fast switching between wired
> and
> wireless. question: is there a setting that can be changed to all this to
> occur? note IP of wireless and wired networks are different ranges.

Jack-MVP

"John" <> wrote in message
news:ECD3562B-F97F-4D8E-A743-...
> Phillip,
>
> I generally agree with you, but Vista and Mac clients do the same things
> on
> our network and do not get this message which leads me to believe that MS
> addressed this issue with the network stack in Vista and that there may
> (or
> may not be) a way to control this behavior in XP.

It doesn't have anything to do with the local machine. It most likey has to
do with dynamic DNS Registration and/or WINS Registration, and that doesn't
even bring into account the Netbios based Master Browse List issues. The
Macs probably don't register themselves to begin with. Can't speak for
Vista, there's no way I can verify it is configured to operate like the XP
machines (even if you think they are,...there a lot of buried details not
easily seen). And on top of that just because Vista and Mac hasn't
"complained" about it does not mean it is "ok" to do it.

> My users are not that
> savvy, even with some education. they see the company wired and wireless
> network as seamless and therefore think that this should just work.

Telling them to simply don't run both at the same time can't be that hard to
understand. Our users always have the wirless nics physically switched off
when in our building. On top of that I never configure their machine for
wireless access to our LAN and don't give them the WPA Key. Our building is
fully cabled, there is no need for wireless. They use the wireless when
traveling

It doesn't have anything to do with being "seamless",...and you don't have
two networks.....you have *one* network,...copper -vs- radio waves are just
two forms of media,...it is no different than mixing copper and fiber optic
on the same LAN,...no is going to think that is two different networks. So
you just cannot run a machine with two Nics on the same LAN, particularly
the same subnet, without odd behavor of some kind, that is the
"norm",....when the machine does not do something odd is the "abnom" and
just "getting lucky". The media being used, copper, fiber optic, radio is
irrelevant.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Phillip Windell

Jack,

i tried that, but did not have any success. I will attempt again on a
different client to test. I have also tried adjusting the adapter priority
in the advanced menu, but that did not work.

It's as if the wireless adapter is hyper sensitive to the change. I'm
wondering if there is a registry setting that can be made to force the
adapter to wait before announcing that there is a duplicate name. Not sure
if that is the purpose of the Metric or the priority settings, but i tried
both and was not successful.



"Jack-MVP" wrote:

> Hi
> May be that configuring the Metrics on the cards would solve the issue.
> http://www.ezlan.net/metrics.html
> Jack (MS, MVP-Networking)
>
> "John" <> wrote in message
> news:0439F1D4-B2C9-42DA-B54F-...
> > we have the following problem.
> > 1. user laptop is connected to the wired network, but wireless also
> > enabled
> > and connected to corporate wifi.
> > 2. user gets up and disconnects from wired network, but is still connected
> > to wireless network.
> > 3. user returns to desk, plugs back into wired network (while still
> > connected to wireless network) and gets 'duplicate name on the network
> > found'
> > error.
> >
> > the error only appears once AND only happens with Windows XP (all at SP3).
> > This does not happen with Vista so my thought is that there is something
> > different in the network stack that allows fast switching between wired
> > and
> > wireless. question: is there a setting that can be changed to all this to
> > occur? note IP of wireless and wired networks are different ranges.
>
>

John

"John" <> wrote in message
news:136F36BD-9AD3-48F5-A5CA-...
> Jack,
>
> i tried that, but did not have any success. I will attempt again on a
> different client to test. I have also tried adjusting the adapter
> priority
> in the advanced menu, but that did not work.
>
> It's as if the wireless adapter is hyper sensitive to the change. I'm
> wondering if there is a registry setting that can be made to force the
> adapter to wait before announcing that there is a duplicate name. Not
> sure
> if that is the purpose of the Metric or the priority settings, but i tried
> both and was not successful.

I think you are wasting you time trying to solve something that isn't
suppose to be done in the first place. I know I can't make you listen if
you don't want to,..it is up to you,...but it is going to be just like I
said it was going to be.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Phillip Windell

I appreciate the advice.

I was able to fix the problem. I disabled NetBIOS over TCP/IP on both the
LAN and wireless adapter and I no longer get the duplicate name error. I'm
going to watch this closely to ensure that changing this doesn't impact
anything else, but early indications are that everything is working properly.



"Phillip Windell" wrote:

> "John" <> wrote in message
> news:136F36BD-9AD3-48F5-A5CA-...
> > Jack,
> >
> > i tried that, but did not have any success. I will attempt again on a
> > different client to test. I have also tried adjusting the adapter
> > priority
> > in the advanced menu, but that did not work.
> >
> > It's as if the wireless adapter is hyper sensitive to the change. I'm
> > wondering if there is a registry setting that can be made to force the
> > adapter to wait before announcing that there is a duplicate name. Not
> > sure
> > if that is the purpose of the Metric or the priority settings, but i tried
> > both and was not successful.
>
> I think you are wasting you time trying to solve something that isn't
> suppose to be done in the first place. I know I can't make you listen if
> you don't want to,..it is up to you,...but it is going to be just like I
> said it was going to be.
>
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

John

Yes that may "dodge" the problem you created,...it doesn't really eliminate
the problem. But if you're happy with it than that is fine I guess.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------



"John" <> wrote in message
news:4A9D5661-63EE-49A1-9C83-...
>I appreciate the advice.
>
> I was able to fix the problem. I disabled NetBIOS over TCP/IP on both the
> LAN and wireless adapter and I no longer get the duplicate name error.
> I'm
> going to watch this closely to ensure that changing this doesn't impact
> anything else, but early indications are that everything is working
> properly.
>
>
>
> "Phillip Windell" wrote:
>
>> "John" <> wrote in message
>> news:136F36BD-9AD3-48F5-A5CA-...
>> > Jack,
>> >
>> > i tried that, but did not have any success. I will attempt again on a
>> > different client to test. I have also tried adjusting the adapter
>> > priority
>> > in the advanced menu, but that did not work.
>> >
>> > It's as if the wireless adapter is hyper sensitive to the change. I'm
>> > wondering if there is a registry setting that can be made to force the
>> > adapter to wait before announcing that there is a duplicate name. Not
>> > sure
>> > if that is the purpose of the Metric or the priority settings, but i
>> > tried
>> > both and was not successful.
>>
>> I think you are wasting you time trying to solve something that isn't
>> suppose to be done in the first place. I know I can't make you listen if
>> you don't want to,..it is up to you,...but it is going to be just like I
>> said it was going to be.
>>
>>
>> --
>> Phillip Windell
>> www.wandtv.com
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>>
>>

Phillip Windell