Business Community > Controllers > Devices not being assigned their fixed IP address
< Controllers

Devices not being assigned their fixed IP address

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Devices not being assigned their fixed IP address

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Devices not being assigned their fixed IP address
Devices not being assigned their fixed IP address
2022-07-27 21:05:27 - last edited 2022-08-02 03:47:15
Model: OC200  
Hardware Version: V1
Firmware Version: 1.17.7 Build 20220623 Rel.35367

I have assigned fixed IP addresses for many of the devices on my network, and I've noticed recently that devices are not being connected to those IP addresses. For example my desktop may be assigned 192.168.1.5, but it keeps connected as 192.168.1.32. I have about half a dozen devices that are doing this now. I can disconnect them from the network, and reconnect, but they still join on the wrong IP, wrong defined as not the set fixed IP. 

 

 

I have updated to the latest 5.3.2 controller firmware and the behavior continues. 

 

I have removed the fixed IP setting for the affected devices, then added it back, and still no change. 

 

 

This seems like a bug, but I'm out of ideas for things to try. 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Devices not being assigned their fixed IP address-Solution
2022-08-02 03:47:11 - last edited 2022-08-02 03:47:15

Dear @cegan09,

 

cegan09 wrote

I have assigned fixed IP addresses for many of the devices on my network, and I've noticed recently that devices are not being connected to those IP addresses. For example my desktop may be assigned 192.168.1.5, but it keeps connected as 192.168.1.32. I have about half a dozen devices that are doing this now. I can disconnect them from the network, and reconnect, but they still join on the wrong IP, wrong defined as not the set fixed IP. 

 

The following solution post has provided the Beta firmware to fix the issue.

 

 Solution  ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#3
Options
4 Reply
Re:Devices not being assigned their fixed IP address
2022-07-27 23:02:52

  @cegan09 It is a bug.

 

See here:

https://community.tp-link.com/en/business/forum/topic/563082

  3  
  3  
#2
Options
Re:Devices not being assigned their fixed IP address-Solution
2022-08-02 03:47:11 - last edited 2022-08-02 03:47:15

Dear @cegan09,

 

cegan09 wrote

I have assigned fixed IP addresses for many of the devices on my network, and I've noticed recently that devices are not being connected to those IP addresses. For example my desktop may be assigned 192.168.1.5, but it keeps connected as 192.168.1.32. I have about half a dozen devices that are doing this now. I can disconnect them from the network, and reconnect, but they still join on the wrong IP, wrong defined as not the set fixed IP. 

 

The following solution post has provided the Beta firmware to fix the issue.

 

 Solution  ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#3
Options
Re:Devices not being assigned their fixed IP address
2023-01-20 20:35:06

  @cegan09 

 

I bought the ER7212 lately and have the same problem with assigning static ip's to LAN-port.

My setup is a ER7212 and on 1 port i have a eap610slim via POE and on an other port a eap615-wall, and on 2 other ports I have POE camera's.

Next to my normal LAN i have a IoT VLAN with a different IP-range (10.0.0.x), where DHCP is on.

 

All wireless clients connected throught the access points get an IP in 10.0.0.x range, but not the LAN-clients (camera's) these still are in the 192.168.0.x - range even when setting a static IP for the IoT LAN.

 

So the fix on the ER7206 seems to be needed on the ER7212 as well.

 

This is the version of my controller:
 

Controller Version: 5.4.20

Model: ER7212PC 1.0

Firmware Version: 1.0.1 Build 20221106 Rel.81436

 

 

Is there a fix for this one? I tried the work around by first changing DHCP range as well, but didn't work here.

 

  0  
  0  
#4
Options
Re:Devices not being assigned their fixed IP address
2023-01-21 10:24:25

  @Pitahaya 

 

you have yet another problem, you try to connect a camera in the router's switch port, you must remember that this router has no possibility to change the PVID, thus you only get default VLAN 1 on the camera, try to connect a switch and set the correct VLAN on the ports of the camera.

 

 

 

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 2247

Replies: 4

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.