Just another "fixed IP not working" thread
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
I have a stupid question but have you turned off the power to the printer, I almost assume you have tried that but I'm asking
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Is the printer the only client that couldn't get the correct IP address?
Did you try to update the driver of the printer?
Please also tell us the model number of the printer.
- Copy Link
- Report Inappropriate Content
@Vincent-TP Unfortunately it is not. The printer is a Neptune 4 Pro but that is irrelevant as many clients get erroneous IP (not the reserved/intended one). Below is a screenshot of a Tuya relay that is wireless, for instance. Also, they don't seem to keep the same IP anyway, it gets refreshed with another one on a random basis, but not with the reserved one (that one simply won't stick). So the fault is definitely not on the client side. There are no other DHCP capable devices in the LAN, by the way, so no conflict.
- Copy Link
- Report Inappropriate Content
I have the same problem with some equipment after replacing ER7206 router with ER707-M2.
- Copy Link
- Report Inappropriate Content
@Andrewspan I wonder if this might be a FW problem with it being a new model and all.
Nevertheless, this is inexcusable, these are meant to be deployed in enterprise environments for crying out loud, where dependability is of the essence. And we are talking some really basic features, not some crazy routing schemes or whatever.
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
ArttVandelay wrote
@Andrewspan I wonder if this might be a FW problem with it being a new model and all.
Nevertheless, this is inexcusable, these are meant to be deployed in enterprise environments for crying out loud, where dependability is of the essence. And we are talking some really basic features, not some crazy routing schemes or whatever.
Both of you please upload a diagram of your network.
Except for the provided firmware version and controller version from the OP, the other person please provide the details of the firmware and controller version.
If possible, you can upload the vanilla backup(not support backup) and compress it with your forum-registered email as the password. Upload it along with your reply. We will look into the issue and test with your provided backup.
- Copy Link
- Report Inappropriate Content
@Clive_A I have meanwhile discovered at least 5 more devices that do not get the desired IP. These are non-vital IoT devices so I never checked because they work anyway. But still. This is part of a larger problem. I honestly hope I am doing something wrong myself, even though there is not much to get wrong. I even tried untcking the static ip box and deleting my clients and re-adding them with the reservations did from scratch via the Services > DHCP > New reservation meniu. I restarted the clients to force a release/refresh. Same result.
Anyway, the files are attached as per your instructions.
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
ArttVandelay wrote
@Clive_A I have meanwhile discovered at least 5 more devices that do not get the desired IP. These are non-vital IoT devices so I never checked because they work anyway. But still. This is part of a larger problem. I honestly hope I am doing something wrong myself, even though there is not much to get wrong. I even tried untcking the static ip box and deleting my clients and re-adding them with the reservations did from scratch via the Services > DHCP > New reservation meniu. I restarted the clients to force a release/refresh. Same result.
Anyway, the files are attached as per your instructions.
Just add another question to confirm, if you configure this to a wired device, will it work? DHCP reservation instead of the fixed IP.
Please let me know before I make my next move.
- Copy Link
- Report Inappropriate Content
@Clive_A No, it does not. Regardless of the connection - wired or wireless. And regardless of the way it's applied - via tick box or via reservation definition. That is what I said.
So do make your next move, by all means. Eagerly awaiting for a conclusion.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 338
Replies: 16
Voters 0
No one has voted for it yet.