I have an odd IP Conflict. In one office I have a laptop and a desktop
computer for some reason the IT that was here before me has the laptop set up
to only use wireless connection even when docked, he then gave the same IP to
the desktop that the laptop onboard NIC had. (this I did not find out till
the other day) The laptop was having issues that is when I noticed that even
when docked it was running on wireless so I enabled the onboard NIC this then
caused a conflict with the desktop comptuer the inetern uses. Now to my
issue.
I changed the IP of the laptop however the desktop still got the ip conflict
so I then changed the IP of the desktop. Once both systems were up and
running on the network I decided to change the desktop back to the old IP as
soon has you do that it gives you a conflict however if you try to ping the
old IP it times out. Can the old IP be stuck someplace in the computer
itself? I thougth maybe it was still on the laptop so I undocked the laptop
and still had the issue on the desktop. I uninstalled and reinstalled the
NIC on the desktop with the exact same results.
"Michelle" <Michelle@discussions.microsoft.com> wrote in message
news:A9E440F9-A1B6-46BF-8769-730CEFD89D3B@microsoft.com...
>I have an odd IP Conflict. In one office I have a laptop and a desktop
> computer for some reason the IT that was here before me has the laptop set
> up
> to only use wireless connection even when docked, he then gave the same IP
> to
> the desktop that the laptop onboard NIC had. (this I did not find out
> till
> the other day) The laptop was having issues that is when I noticed that
> even
> when docked it was running on wireless so I enabled the onboard NIC this
> then
> caused a conflict with the desktop comptuer the inetern uses. Now to my
> issue.
> I changed the IP of the laptop however the desktop still got the ip
> conflict
> so I then changed the IP of the desktop. Once both systems were up and
> running on the network I decided to change the desktop back to the old IP
> as
> soon has you do that it gives you a conflict however if you try to ping
> the
> old IP it times out. Can the old IP be stuck someplace in the computer
> itself? I thougth maybe it was still on the laptop so I undocked the
> laptop
> and still had the issue on the desktop. I uninstalled and reinstalled the
> NIC on the desktop with the exact same results.
You didn't explicitly say you're using STATIC ip assignments, while being
sure to DISABLE DHCP...everywhere. Especially in a wireless environment,
there might be more than one DHCP server in play.
Ping the ip addresses of interest, and observe...carefully. Are there
interlopers?
"Michelle" <Michelle@discussions.microsoft.com> wrote in message
news:A9E440F9-A1B6-46BF-8769-730CEFD89D3B@microsoft.com...
> I have an odd IP Conflict. In one office I have a laptop and a desktop
> computer for some reason the IT that was here before me has the laptop set
up
> to only use wireless connection even when docked, he then gave the same IP
to
> the desktop that the laptop onboard NIC had. (this I did not find out
till
> the other day) The laptop was having issues that is when I noticed that
even
> when docked it was running on wireless so I enabled the onboard NIC this
then
> caused a conflict with the desktop comptuer the inetern uses. Now to my
> issue.
> I changed the IP of the laptop however the desktop still got the ip
conflict
> so I then changed the IP of the desktop. Once both systems were up and
> running on the network I decided to change the desktop back to the old IP
as
> soon has you do that it gives you a conflict however if you try to ping
the
> old IP it times out. Can the old IP be stuck someplace in the computer
> itself? I thougth maybe it was still on the laptop so I undocked the
laptop
> and still had the issue on the desktop. I uninstalled and reinstalled the
> NIC on the desktop with the exact same results.
It may also be that a 'smart' switch (cabling hub) somewhere is memorising
the IP/MAC address relationship and refusing to let go of it. Power-cycling
the offending switch generally fixes this.
On Jan 23, 9:20*am, "John B" <j...@nospam.com> wrote:
> You didn't explicitly say you're using STATIC ip assignments, while being
> sure to DISABLE DHCP...everywhere. * Especially in a wireless environment,
> there might be more than one DHCP server in play.
>
> Ping the ip addresses of interest, and observe...carefully. *Are there
> interlopers?
>
> "Michelle" <Miche...@discussions.microsoft.com> wrote in message
>
> news:A9E440F9-A1B6-46BF-8769-730CEFD89D3B@microsoft.com...
>
>
>
> > I have an odd IP Conflict. *In one office I have a laptop and a desktop
> > computer for some reason the IT that was here before me has the laptop set
> up
> > to only use wireless connection even when docked, he then gave the same IP
> to
> > the desktop that the laptop onboard NIC had. *(this I did not find out
> till
> > the other day) *The laptop was having issues that is when I noticed that
> even
> > when docked it was running on wireless so I enabled the onboard NIC this
> then
> > caused a conflict with the desktop comptuer the inetern uses. *Now to my
> > issue.
> > I changed the IP of the laptop however the desktop still got the ip
> conflict
> > so I then changed the IP of the desktop. *Once both systems were up and
> > running on the network I decided to change the desktop back to the old IP
> as
> > soon has you do that it gives you a conflict however if you try to ping
> the
> > old IP it times out. *Can the old IP be stuck someplace in the computer
> > itself? *I thougth maybe it was still on the laptop so I undocked the
> laptop
> > and still had the issue on the desktop. *I uninstalled and reinstalled the
> > NIC on the desktop with the exact same results.- Hide quoted text -
>
> - Show quoted text -
Can another machine ping? what box does it resolve? Try running
ipconfig /flushdns and then nbtstat -RR from the command prompt on
both boxes. You should be able to set you WNIC to shut down when a
wired is connected.
IP Conflict 
Linear Mode
