TL-WR802N V4 will not connect with iPhone 6S, using the phone as a wifi hotspot
TL-WR802N V4 will not connect with iPhone 6S, using the phone as a wifi hotspot
Model :
Hardware Version :
Firmware Version :
ISP :
Hardware is TL-WR802N(US) Ver. 4.0
s/n: 2178038000645
f/w is factory installed.
iPhone is 6S running iOS 11.2
iPhone 6S works as a wifi hotspot with 4 other devices with no problem. So the iPhone is not the problem.
The TL-WR802N Nano router will connect with an LG Escape 2 Android phone but not with the iPhone 6S.
On your TL-WR802N download page, there are no f/w updates available.
I've now tried about 50 times with all different configurations after reset, to configure the setup to connect to iPhone 6S with no success. I've tried Hotspot mode and Client mode. Quick setups and manual setups.
TL-WR802N V2 is known to work with iPhone 6 series. What did you change in V4????????
This is definitely a compatibility issue with the firmware in the Nano router and there are 10's of millions of iPhone 6 series phones in service.
How soon can we have this fixed with a f/w update?
Anyone have a workaround for this problem???????????
Frustrated to no end.
Hardware Version :
Firmware Version :
ISP :
Hardware is TL-WR802N(US) Ver. 4.0
s/n: 2178038000645
f/w is factory installed.
iPhone is 6S running iOS 11.2
iPhone 6S works as a wifi hotspot with 4 other devices with no problem. So the iPhone is not the problem.
The TL-WR802N Nano router will connect with an LG Escape 2 Android phone but not with the iPhone 6S.
On your TL-WR802N download page, there are no f/w updates available.
I've now tried about 50 times with all different configurations after reset, to configure the setup to connect to iPhone 6S with no success. I've tried Hotspot mode and Client mode. Quick setups and manual setups.
TL-WR802N V2 is known to work with iPhone 6 series. What did you change in V4????????
This is definitely a compatibility issue with the firmware in the Nano router and there are 10's of millions of iPhone 6 series phones in service.
How soon can we have this fixed with a f/w update?
Anyone have a workaround for this problem???????????
Frustrated to no end.