IP conflict - Windows 10

Most likely the ZyXEL is statically set to 192.168.0.2 which is what your computer is using. Change the IP address of your computer first.

Start > Control Panel > Network and Sharing Center
On the top left of the new window, Change adapter Settings.
Right click on Local Area Connection and select properties.
On the new Window, highlight Internet Protocol Version 4 (TCP/IPv4) and then click on the properties button.
Input the following:


Click Ok.

The IP conflict should be gone now. Now you should try and connect to the DoorBell and manually change the IP address there to a higher IP. IPs are usually handed out as the lowest first available. After you change the IP of the DoorBell, change the IPv4 settings on your PC back to Obtain automatically.

So DHCP is running on your router which is giving your computer an IP Address (192.168.0.2 according to your screen shot).

But you don't have to get your IP Address via DHCP, and some devices will have a "static" IP Address, which they set. My guess is that either your doorbell or range extender is set to a static IP address of 192.168.0.2. Your router doesn't know anything about that so when your computer connects and asks for an IP Address (like when you boot or do a ipconfig /renew) your router happily gives it the .0.2 address, and you have a conflict.

You need to plan out your network, make sure any devices that need static IPs have those free, and, critically, make sure your DHCP range doesn't overlap with any static IPs. The DHCP range will be in your router settings "DHCP", it should have a minimum and maximum IP address and it will give out addresses within that range.

Usual practice is to leave the first bunch of IP Addresses free for static devices, then start your range. So I'd suggest
192.168.0.1 Router
192.168.0.2 (whatever device is currently using this - probably range extender)
192.168.0.100 - 192.168.0.200 DHCP range (that gives you 101 IP addresses to give out and allows plenty of space for static devices before it.

What you need to do:
1) Temporarily give your computer a static IP so you can connect to things properly and fix the problem - use something like 192.168.0.222, which is unlikely to be used by something else: http://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-in-xp-vista-or-windows-7/
(use 192.168.0.1 as gateway & DNS, 255.255.255.0 as subnet mask)
2) Connect to your router and change the DNS range (I suggest to .100 -> .200)
3) (if you want to be really safe) check your other devices (like your range extender and doorbell) are either DHCP OR have a unique static addresses outside the DHCP range (like .2, .3, etc).
It's not a bad idea to assign static IPs to devices like range extenders and doorbells, because after a power outage they may well boot quicker than your router, which means they're asking for an IP address before the router is up and running and able to provide one.

Once that's done. You can set your PC back to DHCP and all should work.

or change the beginning of the DHCP pool your router uses. I'm not sure I've ever seen one by default set to start below x.x.x.100
Amazon.com comments on that model that after a certain date, the extender is set to DHCP for its address(which is silly), and they show that the manual states it is actually supposed to be at 192.168.1.2, which is a different subnet than his PC.

I didn't actually read the manual so can't be certain.

I suspect the doorbell thingy.

So that means the doorbell is almost certainly your issue. If I understand you correctly, you can have everything connected just fine, but problems immediately and consistently start when the doorbell is connected?

The doorbell probably has a web interface. The IP Conflict tells you that the doorbell is trying to use 192.168.0.2. So use the instructions above to move your DHCP range to .100 -> .200, then you can put 192.168.0.2 into a web browser and connect to the doorbell. You'll need a username and password. You should be able to find documentation for the doorbell online if it didn't come with any.

Having said that, if the doorbell is the only thing on .2, then moving your DHCP range will fix the problem and there's no reason it shouldn't stay on .2. So in fact, if all goes well, you won't actually need to log in to the doorbell at all.

So with ZyXEL connected (cable) and Doorbell powered off what happens? That will tell you which device is the offender.

You don't have the username and password for the router? That's a shame. Does it belong to them or have you bought it? If you own it (have paid for it as part of a package) they should give you the username+password to get on.
If you have the IP address conflict issue then you may not be able to connect to it (or anthing!). So make sure you're trying when the offending device is not connected.

If you really are unable to get on to the router, you will need to change the IP address of the ZyXEL and doorbell to outside your DHCP range. Follow my link above to set a static IP, then logon to both extender and doorbell to give them new static IPs... something like .250 & 251 are the least likely to cause issues as they should be out of your DHCP range, or at least be right at the top of it and so very unlikely to ever get allocated by your router.

Yeah okay. No way to isolate the issue then.

So set a static IP on the computer as per my first reply. Connect everything. Should work temporarily. You can then log in to whatever is on .0.2 and change its static IP outside the range.
From what you've described then, my guess is that the doorbell uses DHCP and it's actually the range extender that's causing the conflict. Anyway, you'll know when you have a static IP and put 192.168.0.2 into your browser... you'll be able to see which device it is. If you don't have its username+password, google the make/model and find out what the defaults are.

When you disconnect the range extender does your Internet work again?

Can you connect to .0.1 when the network is working properly (with range extended disconnected)?

Bear in mind that your range extender may use two IP addresses, one for it's wireless adapter, and one for it's cable. Connected the range extender may be causing multiple IP address conflicts.

Have you ever got into the settings of the range extender? How did you set it up in the first place?

It's looking like at some point in the set up you've allocated two devices the same IP. The problem is that as soon as you have an IP address conflict anywhere on your network, everything goes to pieces. Particularly if it's a key device like your router which has a conflict.

We need to somehow figure out which IPs are allocated to which devices, but we can't expect that to happen while there's a conflict somewhere on your network.

Can I suggest you download this (free for non-commercial use) tool: http://www.advanced-ip-scanner.com/index1.php?utm_expid=62919999-31.9JLRl0OpRDKOkzhnLNA-2A.1&utm_referrer=https%3A%2F%2Fwww.google.com.au%2F

It will tell you what devices are on your network. BUT, don't expect it to work when there's a conflict.

So... run it without the extender connected and record the results. [That will tell you what IPs are in use by your "normal" network, i.e. your network minus the extender & doorbell].

Then, is there a way you can get the cable that runs between router & extender to go Extender -> PC instead? If you can, do that, then power off the router (so extender can't connect via wifi either) and run the tool again. [That will tell you which IPs are in use by your extender & doorbell]

Then, hopefully, we'll know which devices are conflicting with which and we can start to figure out how to fix it.

Okay, well it certainly seems like your DHCP range starts at 0.2, which is less than ideal. But you say that even without the range extender connected you can't put 192.168.0.1 into a web browser? That gets a connection time out? That shouldn't happen and is worth chasing your ISP (if they set it up) to try and get access to it.

Having said that, we can probably still work around it in the meantime.

In the attachment there's 192.168.0.7 listed as a "ZyXEL"... is that the range extender that's causing issues? Or have you got more than one? Can you connect to it by putting 192.168.0.7 into a web browser?

Try that and let me know how you go...

So what IP addresses are the range extender set to? It should have a wireless IP (which we know is 0.7 because that's how you've connected to it) and a cable/LAN IP - which could well be 0.2 OR 0.1 and the one causing all the problems. See if you can change that to something well out-of-range - like .250...

**edit -> RE the router (which is technically a wireless modem/router - all of the above), if that's your ISP's policy then I guess that's that. Personally I wouldn't have anything on my network that I didn't have access to and I would expect and demand that from my ISP... but that's my view. It might not matter though if you try the above.

Okay. I think I know what's going on.

That LAN port on the range extender is to connect a device which doesn't have wireless to your wireless extender. So let's say you have a desktop which doesn't have wireless and you need it to connect to your wireless network... then you can set up the extender and connect its ethernet port to the PC's ethernet port and you're good to go.

The way you've set it up you've created a loop in your network. The extender is connected to your network twice... once via wireless (which is what an extender does), and then again via the ethernet port. A loop = packet storm and total mess on standard consumer switches. Sometimes packets can still get through, but it's a total mess with massive packet loss, meaning sporadic connections and dropouts... which seems to perfectly describe your symptoms when that cable is connected.

I had a look at the manual and that wireless extender will only connect to your router wirelessly. So if you want to keep using it you'll need to find a position for it in your house that maintains a sufficient signal both from the extender to your modem/router, but also to the wifi doorbell.

What you're currently doing actually requires a simple Wireless Access Point. That would allow you to run an ethernet cable between your modem/router and your Access Point, with the Access Point then providing a separate wireless network which you could connect your wifi doorbell to.