iPhone wifi router conflict issue!

One common cause of address conflicts is when a system comes back online after an extended period in stand-by or hibernate mode, especially if the system was previously part of another network (e.g. an iphone brought home). A conflict will promptly occur if the address the system was previously configured with is the same as one that's already in use on the network. These conflicts tend to work themselves out. IP conflicts tend to eventually work themselves out in DHCP environments because systems issues repeated requests for valid addresses. But since the process can take a while and doesn't always work as planned, one way to hasten a fix is by manually entering IPCONFIG /RELEASE and IPCONFIG /RENEW from a command prompt (restarting a system accomplishes the same thing but takes a lot longer).

If the conflict persists even after renewing the IP address, it may be because your system's been re-issued the same address it already had and another system on your network is the source of the problem. You can get a clue about the offender by checking the System Log within the Windows Event Viewer (which you can get to via Start|Control Panel| Administrative Tools|Event Viewer) and looking for a DHCP error entry. The entry will list a network address (actually a MAC address) which you can use to identify the conflicting device, either by running IPCONFIG / ALL on a Windows system or checking the label on the back or underside of a non-PC device. Performing a IPCONFIG release and renew or restarting the other device should set things right. If not, restarting your router should do the trick as it will reset the DHCP server and force all systems to request new IP addresses.

1. Turn off everything on the network, ALL the machines and any other network device like network printers and NAS drives.
2. Turn off the router and modem.
3. Turn on the modem, wait for a steady data light.
4. Turn on the router, wait two minutes.
5. Turn on the network devices and computers, one at a time.

Enjoy!

Don't worry, you solved your problem. I was trying to explain why it happened & the fact that is not unusual & how to solve it.

You're welcome.

Another thing that could be at play is a double-NAT issue. That term probably won't make sense and doesn't have to -- but basically if your wireless access point is ALSO designed to serve as a router, then you have your wired router assigning IP addresses and the wifi access point or router also trying to assign IP addresses. If this might be the case, check your wifi access point's documentation to see how to disable NAT and DHCP on the access point.