Just another "fixed IP not working" thread
As you can clearly see in my first pic, assigning MAC based IPs in OC200 with the ER707-M2 v1.20 router is definetly hit and miss. I have a very basic network and most clients do get the expected IP - all ethernet wired, all same and only (main)VLAN. But this device (my 3d printer) has had enough with the assigned IP and decided to go for another one. I tried to reset/release/renew/refresh 100 times to no avail. Tried to delete and readd, tried to erase from known devices, I think I tried everything. My MAC is correct. DHCP enabled on printer. DHCP pool includes my "to be" reservation. No MAC IP binding. Apparently other folks have shared my frustration but I think it got solved with a FW update eventually, However, I am on last update both on my OC200 and my ER707. So if any more technically enclined than me feel to chip in, I would very much appreciate it. Better yet, if any TPLink tech has a solution to my problem, I am all ears - well, eyes.Please help.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks for posting in our business forum.
ArttVandelay wrote
@Clive_A That is how I used to do it also. And 10 other desperate ways as of late. This is not the first time I am getting an IP reservation in a network. Never had a problem myself as this is one of the simplest most basic operations to be done with DHCP. Everybody could do it, you don't have to be like a CCNA engineer to pair a darn MAC with the desired IP for God's sake. I never ever thought of it not working, it was one of those do and forget thing.
So now about half of my clients, random AP, random connection type, random time, have other IP from the one I reserved. I reboot the router and controller, I delete the reservation, I reassign it, then power cycle the client and then it gets the correct IP. Easiest is to just pull down the main power breaker and have all the building power cycle. Which is obviously unpleasant. Then the correct IPs get allocated for a while. My lease time is 120 mins, the default. I tried with shorter or longer with no luck. Eventually they do get changed randomly.
Have you seen the other threads about this? There are quite a few. Seems I am not the first to having this problem. I see main culprit was FW related. And after the update it got sorted. So as I previously mentioned, I think this is the case now with the ER707M2 being a rather new model. But I see no FW updates.
I guess this week I will RMA all my shiny new Omada equipment and switch back to Unifi - which was rock solid but had other flaws. Or Cisco even, probably pre-owned (unless I decide to sell the house and car as well).
So thanks again for the intention, but this is getting rather silly.
Yes. We have noticed that. Unfortunately, since the first report till now, we only have one customer remote desktop successfully. 4 out of 6 cases have been created. But only 1 customer has cooperated with our dev for a debug.
I have not received a diagnosis report on his case yet. I will surely update all 6 cases on the forum once we make progress. So far, 3 have not replied to my email. 2 pending for new tickets.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 590
Replies: 21
Voters 0
No one has voted for it yet.