peristsant (clientside?) ip address conflict

[themadjester]

This is weird, I know what an IP address conflict is, and how to avoid it, but this problem seems atypical - and apparently client side?

Basically I have a router internet network, it is DHCP and the range [was] 100-199

Now, to my knowledge myself and everyone else on the network is using DHCP (non techies).

some things I have tried are:
- I changed the address range from 100-199 to 150-199 to force my laptop to obtain a new IP (and not the same one when it releases)
-I reset the router and upgraded the firmware

this issue happens only to me, and I had the same issue before on another wireless network (around the time) it cropped up were I am currently. Interestingly this network I connected to had trouble with the ISP and was down at this time. I noticed the ip address conflict, but I cant remember if it had cropped up sooner... I think not.
I also have a suspicion that the 2nd IP address in conflict is somehow another one associated with my device.

Many people on the internet say that this problem is never client side, and is always a network issue, but I am having my doubts.

I should also note that I have internet access, but would like to get this resolved because it seems indicative of another problem.

[ShaneA]

I would first ping a random IP address to get a free one that has no reply. Then set the IP of your LT to static and see what the results are.

Another question I have is, do you have a server in your environment?

You might need to flush out the DHCP!!

[themadjester]

I had though i replied to this half a week ago but network connection is incredibly unstable and my reply apparently did not make it.

by servers I believe you mean a mail server or a print server or some general machine that is doing the routing.
luckily to simplify things this is not the case. I am however dual booting and have apache installed on both partitions if you mean that kind of server.

I have changed my ip server times to addresses outside the DHCP range, since there are a limited number of other users, none of which know what DCHP or an IP address is, I feel confident that my the IP conflict is not an actual conflict.

This same issue also occurs if I use this laptop with another wireless network, (and use DHCP). For this reason it appears to somehow be all me.

I tried to google and figure out how one might flush out the DHCP so-to speak, but have been unsuccessful in understanding this. Do you mean something like arp-d? as I mentioned I am pretty sure the fault is on the laptop side of things.\

Edit: every time the connection is made, the Ip address conflict warning appears, I click it away and the internet work. I am not sure if its my router or this conflict but 5 minutes to 1/2 hour later I lsoe the connection as I eluded to at the beginning of the post.hopeful this helps... please help.. this iza makin me CRAZY!...!
Thanks!

[DonRayner]

open a cmd window and type the following without the quotes

"ipconfig/release" then press enter
"ipconfig/renew" then press enter

"ipconfig/all" will give you the details of your settings.

If you get an error to the effect that the ip can't be released that means that your wireless is set with a static IP.

[themadjester]

Yea, I tried that when the issue began.

I have tried both using a static and a dynamic IP address, I get the same error both ways. I have a done the ipconfig -release/renew stuff before.

Currently I am using a static IP, and I know there is no address conflict with the address as it is out of the DHCP range of the router, and no one else could/ would be using the address (I have changed it a number of times to be sure).

I get this error no matter what. It doesn't matter if I am on my normal wireless LAN or someone elses, if I am static or dynamic. I even get the error when my laptop starts and stops for the login screen. I think it even happens if there is no network present.

I have considered re-installing my network drivers, but they worked for years before without any problems, and I am concerned that I might lose internet if I get the wrong ones and not be able to connect and try again. I also had a very difficult time finding drivers a year ago after I formatted/reinstalled XP without the manufacturers CD, and the drivers on the CD seem difficult/impossible to access from windows. Is this worth the effect/risk to try?

Also does anyone know of any malware that can cause this issue? I have not noticed anything suspicious (other than this) but this issue is very atypical so might need to think outside the box. I am getting pretty close to re-imaging the laptop, but if its a relatively simple fix I would like to avoid that.

Edit: In the past I have had IP stack corruption problems and had to to the winsock -reset gambit. Could this be related?

[DonRayner]

This doesn't happen to be a Vista OS does it?

[themadjester]

nope. death before vista IMO >.>

[DonRayner]

Has IPv6 been installed on the laptop? You can check it by opening a cmd window and typing "ping6 -n 5 ::1" If you get a reply from ::1 then IPv6 is installed, if you get "Unable to contact...." not then it's not installed and can't be contributing to your problem.

If it is installed you can try removing it by typing "netsh int ipv6 uninstall". If you ever need to reinstall it the command is "ipv6 install"

[themadjester]

It was installed. As suggested I uninstalled it however the problem persists. I am using XP as I mentioned but does anyone here know how this problem manifests itself under vista?
I ask because I am assuming no other network users have this problem, however perhaps Vista is not so verbose as XP.

[themadjester]

I am now somewhat certain that this occurs only when the wireless card is enabled

[DonRayner]

It almost sounds like your built in NIC and wireless adapter are in conflict with each other. You could try disabling the NIC and then connecting with the wireless to see if the problem persists.

Also what is performing your DHCP assignment, Is is a server or router? Could it be possible that your wireless router is acting as DHCP when you also have another DHCP server/router on your network? Could it be the wireless router's address that is in conflict with another one?