Need help with Omada network
Hello?
Since moved home wireless network to Omada I have series of issues.
I have OC200 with last firmware 1.34.2 Build 20250110 Rel.75707 and two EAP230-Wall(EU) and one EAP235-Wall(EU) two VLANs with home twork and IOT network. IOT network has only access to Internet, with no access to home network.
Home network is 2,4 and 5 GHz with WPA2 key, and IOT network is 2,4 GHz.
Well, I have problems with lot of endpoints which I cannot connect to Wi-Fi network.
All of my PCs, notebooks, cellular phones work correctly, but . . .
- I cannot send youtube video from my cellular phone to TV (on Philips and LG TV), although they are connected both to same Wi-Fi network,
- I cannot connect my air conditioner to any Wi-Fi network,
- I cannot connect my smart switches to any Wi-Fi network,
- I cannot connect my robot vacuum cleaner to any Wi-Fi network,
- I cannot access my DLNA server from TV.
All above devices are factory reseted, (A/C is brand new), and tested on Mikrotik Wi-Fi AP.
Only IOT device that is connected successfully to Wi-Fi is heating thermostate, all five of them.
Thanks for your suggestions.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @mcatic
Thank you for reaching out to the TP-Link community and providing detailed information about your network setup and issues. Based on your description, it seems like there are some configuration challenges that might be causing these connectivity problems. Let me address each issue systematically and provide potential solutions.
---
**1. YouTube Casting Issue (Phone to TV)**
- Enable IGMP snooping under the LAN Networ settings of the connected VLAN.
---
**2. Air Conditioner, Smart Switches, and Robot Vacuum Cleaner Connectivity Issues**
These devices often have limited Wi-Fi capabilities and may struggle with certain configurations:
- **Wi-Fi Band Compatibility:** Many IoT devices only support 2.4 GHz networks and may not work well with dual-band or 5 GHz-only configurations.
- **WPA2 Security:** Some older IoT devices may not fully support WPA2 encryption or may require additional configuration steps.
- **DHCP Lease Issues:** Ensure that your DHCP server is assigning IP addresses correctly and that there are no conflicts.
**Solution:**
- Create a dedicated SSID for your IoT devices on the 2.4 GHz band with WPA2 encryption.
- Simplify the SSID name and password (avoid special characters) to ensure compatibility with IoT devices.
- Verify that the DHCP pool has enough available IP addresses for all devices.
- If possible, test connecting these devices to a guest network temporarily to isolate the issue.
---
**3. DLNA Server Access Issue**
The inability to access your DLNA server from the TV could be due to:
- **VLAN Restrictions:** If your TV and DLNA server are on different VLANs, inter-VLAN communication may be blocked.
- **Firewall Rules:** Ensure that the Omada Controller’s firewall is not blocking the necessary ports for DLNA traffic (e.g., TCP/UDP ports 1900, 8200).
**Solution:**
- Place both the TV and DLNA server on the same VLAN if possible.
- Check the firewall settings in the Omada Controller and allow traffic on the required DLNA ports.
- Test accessing the DLNA server from another device on the same VLAN to confirm the issue.
---
**4. Thermostats Working Fine**
The fact that your thermostats are connecting successfully suggests that your IoT VLAN and 2.4 GHz network are functioning correctly for at least some devices. This reinforces the idea that the issue lies in specific device compatibility or configuration rather than a fundamental network problem.
---
**General Recommendations**
1. **Update Firmware:** Ensure all your EAP devices and the OC200 controller are running the latest firmware.
2. **Test with Default Settings:** Temporarily reset your Omada Controller to default settings and reconfigure a minimal setup to see if the issues persist.
3. **Isolate Devices:** Test one IoT device at a time to rule out interference or resource exhaustion on the network.
---
If the above solutions do not resolve your issues, please provide the following additional details so we can assist you further:
- The exact error messages or behavior observed when trying to connect the problematic devices.
- A screenshot of your VLAN and SSID configurations in the Omada Controller.
- Any specific firewall or access control rules you have applied.
- Copy Link
- Report Inappropriate Content
Hi @mcatic
Thank you for reaching out to the TP-Link community and providing detailed information about your network setup and issues. Based on your description, it seems like there are some configuration challenges that might be causing these connectivity problems. Let me address each issue systematically and provide potential solutions.
---
**1. YouTube Casting Issue (Phone to TV)**
- Enable IGMP snooping under the LAN Networ settings of the connected VLAN.
---
**2. Air Conditioner, Smart Switches, and Robot Vacuum Cleaner Connectivity Issues**
These devices often have limited Wi-Fi capabilities and may struggle with certain configurations:
- **Wi-Fi Band Compatibility:** Many IoT devices only support 2.4 GHz networks and may not work well with dual-band or 5 GHz-only configurations.
- **WPA2 Security:** Some older IoT devices may not fully support WPA2 encryption or may require additional configuration steps.
- **DHCP Lease Issues:** Ensure that your DHCP server is assigning IP addresses correctly and that there are no conflicts.
**Solution:**
- Create a dedicated SSID for your IoT devices on the 2.4 GHz band with WPA2 encryption.
- Simplify the SSID name and password (avoid special characters) to ensure compatibility with IoT devices.
- Verify that the DHCP pool has enough available IP addresses for all devices.
- If possible, test connecting these devices to a guest network temporarily to isolate the issue.
---
**3. DLNA Server Access Issue**
The inability to access your DLNA server from the TV could be due to:
- **VLAN Restrictions:** If your TV and DLNA server are on different VLANs, inter-VLAN communication may be blocked.
- **Firewall Rules:** Ensure that the Omada Controller’s firewall is not blocking the necessary ports for DLNA traffic (e.g., TCP/UDP ports 1900, 8200).
**Solution:**
- Place both the TV and DLNA server on the same VLAN if possible.
- Check the firewall settings in the Omada Controller and allow traffic on the required DLNA ports.
- Test accessing the DLNA server from another device on the same VLAN to confirm the issue.
---
**4. Thermostats Working Fine**
The fact that your thermostats are connecting successfully suggests that your IoT VLAN and 2.4 GHz network are functioning correctly for at least some devices. This reinforces the idea that the issue lies in specific device compatibility or configuration rather than a fundamental network problem.
---
**General Recommendations**
1. **Update Firmware:** Ensure all your EAP devices and the OC200 controller are running the latest firmware.
2. **Test with Default Settings:** Temporarily reset your Omada Controller to default settings and reconfigure a minimal setup to see if the issues persist.
3. **Isolate Devices:** Test one IoT device at a time to rule out interference or resource exhaustion on the network.
---
If the above solutions do not resolve your issues, please provide the following additional details so we can assist you further:
- The exact error messages or behavior observed when trying to connect the problematic devices.
- A screenshot of your VLAN and SSID configurations in the Omada Controller.
- Any specific firewall or access control rules you have applied.
- Copy Link
- Report Inappropriate Content
Thank you for exhaustive answer.
This time I am very busy with business obligations so will check it in next few days.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Vincent, here is little update.
1st of all, my router was of one of Mikrotik devices, everything else was Tp-Link.
In the meantime I bought new Omada gateway and changed my Mikrotik with ER605 gateway. This was very painfull, I spent almost all day trying to get ne setup to work.
Firstly, i just removed Mikrotik and installed ER605 with same settings - nothing was changed.
Next, resetted all equipment (OC200, ER605 and SG2016) to factory default settings, put new passwords, SSIDs, WPA2 keys, adopted all devices to Omada controller, and somehow my ER605 took default subnet settings so everything became unusable.
Further step was to exclude ER605 from Omada controller, set it up again as standalone piece of equipment.
Now, the first goal is that I could connect one of my light switchers to IoT network.
I will try in next few days connect other equipment and will bring back informations here.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 219
Replies: 4
Voters 0
No one has voted for it yet.