Wiser has duplicate IP

My Wiser is configured with a static IP outside the DHCP range of the router. I relocated my Wiser to another room today and after powering it up again I was unable to connect to it. Using a network scanner App it reported the Wiser had duplicate IP, the static IP assigned to it and another within the DHCP range. I'm unable to connect to the Wiser at either IP.

What I don't understand is how the Wiser has ended up with duplicate IP when it has been configured with static. The other thing is, how do I sort this issue out without having to revert to factory default reset?

 

Hi Brodricj,

Assume you resolved this by now. Was it the bridging table in your Ethernet switch (or the 'switch' Layer 2 section of your internet router) not updating properly when you move between ports? That is quite often the problem.

Brad

 

No, problem not resolved yet.

The Wiser and PCI were connected to the same switch: functioned normally.

I put the Wiser on a different switch and left the PCI where it was: can't contact Wiser, network scanner says it has duplicate IP. Can see the PCI on the network.

Piggybacked the Wiser and PCI together using the bridge (i.e. both connected to the same switch): now can't see the PCI or the Wiser on the network.

 

Hi BrodricJ,

Sounds annoying!! How have you lived for so long without your Wiser? I would miss mine dreadfully in about 2 hours!!

I am sure you have checked but on a basic level, it sounds like everything you move to Switch 2 stops working. It's not dead is it? Like the parrot!! (Sorry about obtuse Monty Python sketch reference.)

Have you reset both switches to clean up their bridging tables (and any Layer 3 - IP addressing ARP caching etc they may have that could have gone AWOL?)?

Another possibility is that some 100BaseTX devices can have auto-negotiation issues with certain switches. This can cause one end to go half duplex and one full duplex wrecking the comms or at best making it incredibly slow.

Though I am certain you would have checked these simple issues already but it shouldn't be this hard. The other possibility is that you actually DO have a duplicate IP address and something on your network has picked up the Wiser's address by mistake. Some network devices come with a pre-programmed local address in them eg Telstra Cable Modems 192.168.100.1 .

If it's not these network hardware style issues, for further diags it will require the full listing of IP addressing, def gateway setting, Wiser setup settings etc. eg. You have it set for access from LAN?

Let my know if you find something!

All the best,

Brad

 

I'm just going to bite the bullet and reset Wiser back to factory settings and start again. I have overhauled my whole network since the Wiser went whacky on me. When everything was behaving normally I could access Wiser in the normal way both from WAN and LAN side. Then something in the router went haywire and I could no longer access Wiser from the WAN side. Problem could not be resolved and things got worse when I connected Wiser to a different switch and then I encounted the duplicate IP problem. As the router was giving me grief with port forwarding I have completely overhauled my network. Said router I've put in bridging mode and using it as modem only. I bought a Fortinet Fortigate 50B which is now my router/dhcp server/firewall. Also bought a Pakedge POE managed switch and a Pakedge AV priority unmanaged switch and changed all my cabling to Cat6 STP. I'm also using a Pakedge access point so all the hardware on my home network now is Enterprise class (about $6k worth of hardware upgrade all precipitated by my initial Wiser problem!).

 

All very whacky, I've been seeing some weird issues on my network recently. Anyway, I reset Wiser back to factory settings and normal function has been restored. I didn't realize that a factory reset doesn't erase the Wiser project so it was no effort in the end to get it back up and running.

Oops, I spoke too soon. The Wiser was working, then I updated the firmware file via PICED 4.11.1, the Wiser restarted in the normal way, but now it doesn't work. I can ping the Wiser at its LAN IP and get a reply but I can't open it's web management, and I can't open it with the Wiser App. I can still connect to the Wiser in PICED and upload its config file, but I can't connect to CBUS in simulation mode (the in-line PCI is connected to the wiser via the busbar). I have tried restarting Wiser but no success with it working as per pre-firmware update. Any clues?

 

$6k upgrade due to your Wiser problem!!! Go on, admit it. You just wanted all new hardware and were looking for an excuse.....

I have found that after the new firmware is uploaded, and then the project it has at times come back with a 'Red Hand' when first trying to access. Copying the project again fixed it for me though both times I saw it and once again today at another client's site.

I would check that your original project settings haven't 'moved'

Particularly that the Wiser IP in PICED project matches your static address, that it is still ticked for 'Access Wiser from LAN ports', that Projector control is enabled in PICED project etc.

Colin on the forum recently described a repair technique where setting the Projector slide in Wiser GUI to off, letting it reboot and then switching back on cleaned out a data register that may have become corrupted in upgrades etc. But you need to be in first to do that of course.

Been a long day, so need to call it a night!!

Brad

 

all sorted, it was a socket authentication failure that was preventing me opening the Wiser. So to summarize I couldn't open the Wiser at 192.168.2.1 simply because of a password, but I could open 192.168.2.1/setupDHCP.htm without needing a password.

 

Hi Brodricj,

Glad to hear that. Assume the password changed back to default in the Wiser when you did the factory reset so it no longer matched the 'Unit password' in the PICED project?

Brad

 

Yes, one of those obvious problems that aren't so obvious until after you work out the problem! I haven't seen this behavior in other Wiser firmware updates so it's something I'll be mindful of next time around.

....but I do have a new issue. Trying to access Wiser from the WAN side I'm seeing the router login page and not the Wiser. I have transposed my port forwarding rules exactly as they were in my DLINK router (which worked) into my new Fortinet router (which is not behaving as expected). So I'm not sure how to tackle this one....

 

Hi BrodricJ,

Was just about to get some shut eye. Oh well!! One last post won't kill me.

By 'seeing the router' I assume you mean you are getting your new external router's page rather than the Wiser. This is probably as you will find that your external router uses port 8080 as its external management port. The easiest way around this is to forward to a different WAN port on the Wiser 'router' sections management port. In the Wiser router/admin interface, set the 'management port' from 8080 to something different, like 9495 etc and then just use that address for your port forward through your new external router. Put it into your iPhone WAN setup as x.x.x.x:YYYY where x is your external IP address and YYYY is the new port ie 9495 in the example.

Some routers won't let you fully turn off their 8080 remote mgmt ports in software, and so forwarding that port from the external to internal side doesn't work quite as you might expect just for that port.

Look in your external router for its mgmt port, and you could try making that something different to start with, like 7070 or something. If this works, your old port forwards for 8080 should work as they did before and the Wiser config won't need changing.

All the best,

Brad