Solution TCP Connections May Fail Between Different VLANs On The Same EAP650/ EAP670/ EAP653 [Case Closed]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Updated as of Jan 30th 2023:
The official firmware has been released to fix the issue mentioned in this post.
Please follow the direct download link below for manual upgrade, or visit TP-Link regional official website for updates.
EAP653(EU/US)_V1_1.0.4 Build 20220921 Full Release Note >
EAP650(EU/US)_V1_1.0.6 Build 20220921 Full Release Note >
EAP670(EU/US)_V1_1.0.6 Build 20220921 Full Release Note >
Notes:
(1) The above firmware is applied to v1/v1.20/v1.26.
(2) The above firmware can be installed on the EU version and US version.
(3) The release notes above didn't mention it has fixed the TCP connection issue but the above firmware does have fixed it.
If you still have the TCP connection failure issue, it might be a different case, please don't hesitate to Start a New Thread from HERE.
To get better assistance from Community, you may check Tips For Efficiently Reporting an Issue In The Community.
Thank you for your attention. See you in the forums soon!
This Article Applies to:
EAP650 v1/ v1.20/ v1.26
EAP670 v1/ v1.20/ v1.26
EAP653 v1/ v1.6
Issue Description/Phenomenon:
Recently we received feedback that TCP connections (such as Remote Desktop) failed between clients connected to different VLAN SSIDs on the same EAP650/ EAP670/ EAP653. Here is the case details.
Topology & Setup:
Internet --- Router --- EAP650 SSID1 & SSID2 ))) ((( PC1 & PC2
VLAN1 (SSID1): 192.168.1.x/24
VLAN3 (SSID3): 192.168.3.x/24
Problem:
-
When the PC1 & PC2 are connected to the different SSIDs respectively, TCP connections (such as remote desktop) are broken between the two for anything beyond a simple network ping, i.e., the client on VLAN1 can ping the client on VLAN3 but the attempt to open a remote desktop connection ends up a failure.
-
When two PCs are each connected to the same VLAN SSID, the Remote Desktop connection works as expected.
Related Threads:
Issues with tcp connections between VLANs on the same AP
Available Solutions:
The issue has been located and TP-Link has released the official firmware to resolve the issue.
EAP653(EU/US)_V1_1.0.4 Build 20220921 Full Release Note >
EAP650(EU/US)_V1_1.0.6 Build 20220921 Full Release Note >
EAP670(EU/US)_V1_1.0.6 Build 20220921 Full Release Note >
Notes:
(1) The above firmware is applied to v1/v1.20/v1.26.
(2) The above firmware can be installed on the EU version and US version.
(3) The release notes above didn't mention it has fixed the TCP connection issue but the above firmware does have fixed it.
If you are looking for a quick solution, you may install the Beta firmware below to fix the issue temporarily.
Note: Please be sure you have read the Beta Test Agreement before proceeding!
For EAP650 v1/ v1.20/ v1.26:
EAP650_v1_1.0.0_Build20220804(Beta)
For EAP653 v1/ v1.6:
EAP653_v1_1.0.0_Build20220804(Beta)
For EAP670 v1/ v1.20/ v1.26:
EAP670_v1_1.0.0_Build20220804(Beta)
Note: the above Beta firmware has added the PPSK support.
Thank you for your attention!
Feedback:
If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
If there is anything unclear in this solution post, please feel free to comment below.
Thank you in advance for your valued feedback!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Fae Is that how TP-Link helps customers that buy the expensives accesspoint ????????
Could you please reply?!
- Copy Link
- Report Inappropriate Content
And again a week without any feedback! What's going on with TP Link?!
It's not a business product from this point of view. With such bad support (no support) and slow updates you never will get Omada into place against UniFi System. So sad to see.
- Copy Link
- Report Inappropriate Content
I'm not going to comment on UniFi support because I've never needed to use them 
despite the fact that I have 50-60 UniFi sites, it just works with little problems.
Maybe the long wait for firmware is because they are actually testing this time :-) just kidding.
And @Fae it would be nice if you could update us on the forum about the progress plans of TP-Link and when we can expect to get new features on devices that are not supported by new features on the controller.
Now almost everything I have only in beta and has been for a very very long time.
- Copy Link
- Report Inappropriate Content
@Fae are you alive?
- Copy Link
- Report Inappropriate Content
@Fae I think the EAP670 Series is a big scam from TP-Link
- Copy Link
- Report Inappropriate Content
@Christian2705 He is. He is writing within other topics. So overall not a good sign from TP Link NOT to answer within this topic.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Spryde Maybe we should open a new thread? 
- Copy Link
- Report Inappropriate Content
@Fae Any update on a release without bugs (new final release?) for EAP650? We are waiting since months. For such a stupid and annoying bug there must be a new release within days!
- Copy Link
- Report Inappropriate Content
@Spryde Any update on when you'll ask for another update?
Yes, it's very disappointing and tarnishing this bug hasn't been addressed, you've aired that grievance and I share it. But only thing to do now is wait for the release. I subscribe to this thread so that I know as soon as the release is issued. All the notifications of people asking for updates are unnecessary. Fae is active, so they'll respond when there's an update, which means the answer to your question is no, there are not any updates. I don't see the value in Fae replying replying "No, there are no updates" every time you ask as it just sends further unnecessary notifications and wastes everyone's time. as no new information is relayed.
@Fae Could we consider locking this thread?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 10636
Replies: 32
Voters 2
