Wired static clients appear in controller with invalid address
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I'm having a very similar issue to this topic:
https://community.tp-link.com/en/business/forum/topic/187180
All my clients are wired, however. I am setting static IP addresses for each one: 192.168.10.x. Some of them appear with these correct addresses in the Omada Controller. However, others appear with 169.254.x.x addresses. The ones with these link local addresses still work fine and connect to the internet with no issues, but it would be nice if I could identify them correctly in the controller software. These are all Windows 10 computers. The ones that appear correct are newer machines, but all of them are running Windows 10, fully updated.
Any ideas?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@strells What gateway are you using for IP assignment, or is the static IP being set on the computer?
- Copy Link
- Report Inappropriate Content
@JoeSea static addresses are set on each individual computer.
- Copy Link
- Report Inappropriate Content
@strells It sounds like the gateway is already handing out those IP addresses you want to be static to someone else under dynamic allocation, since the gateway probably doesn't have a reservation for the IPs. So Windows gets a IP error from the gateway for conflict, and sets a local IP.
- Copy Link
- Report Inappropriate Content
@JoeSea I don't have DHCP enabled so how is that possible?
- Copy Link
- Report Inappropriate Content
@strells Oh wow, ok, I've not heard of a network that is fully static since the 90's. But it still is most likely a double IP assignment conflict with another client.
- Copy Link
- Report Inappropriate Content
@JoeSea I have a VPN IPSec tunnel setup and I need to access each individual machine, thus the static addresses. I can guarantee I don't have any duplicated addresses or I'd be having some real issues with my setup.
- Copy Link
- Report Inappropriate Content
@strells I'm not the best at VPNs, but could there be conflict across the tunnel if both sides are using the same subnet?
- Copy Link
- Report Inappropriate Content
@JoeSea the other side isn't using the same subnet. The whole thing doesn't make sense.
- Copy Link
- Report Inappropriate Content
strells wrote
I'm having a very similar issue to this topic:
https://community.tp-link.com/en/business/forum/topic/187180
All my clients are wired, however. I am setting static IP addresses for each one: 192.168.10.x. Some of them appear with these correct addresses in the Omada Controller. However, others appear with 169.254.x.x addresses. The ones with these link local addresses still work fine and connect to the internet with no issues, but it would be nice if I could identify them correctly in the controller software. These are all Windows 10 computers. The ones that appear correct are newer machines, but all of them are running Windows 10, fully updated.
Any ideas?
Dear @strells
What is the model number of your router? And the switch?
If possible, please share us how you connect the whole network, so I can run some test on my end.
- Copy Link
- Report Inappropriate Content
@Hank21 hi missed this until now. The router is an ER605. The switch is a Cisco high end device, I 9300 series (I'm forgetting right now which it is). The router connects between ports 1 and 2 of the switch to feed to the other 46 ports.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 663
Replies: 10
Voters 1
