Can't connect using SSH to my local server from external host and vice versa
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Can't connect using SSH to my local server from external host and vice versa
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
When I tried to connect from some local host with my server everything works fine but when i try to do the same but with an external host it's impossible.
In this point, I can say that the server firewall and server pot is working good because I open the ports in the server an also I disconnet de server firewall.
Next, when I try to connect to my server with external host the ssh client tell me that the password authentication works but the conexion close fot timeout reasons or failed waiting for channel success
In the other way, when I try to connect to my external server (AWS instance) via SSH from my home, the SSH client cant connect and telling me "client_loop: send disconnect: Broken pipe"
But when I to connect to my external server (AWS instance) using my phone like a router, I can do it
I try disconnecting every protection in the router but it doesn't works
I also open the ports in the port forwarding and works for http (port 80) but not for ssh, I try changing de default port (port 22) for other and it doesn't works, I try with DMZ and also doesn't works
I have the same problem when I use Cisco Webex videocall, it can't establish the connection and I have to use my phone like a router when i need to use Cisco Webex videocalls
I also try restarting all the default settings and updating the router with the last version but it still doesn't work
Someone have some idea why is this happen?
I really appreciate any answer.
Thank you very much for your time and have a nice day
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @shberge, @LarryMerino,
shberge wrote
I have no idea, have you tried to upgrade to the beta I left a link to earlier up in the thread? this is the one I use when I test. try and installed it to see.
I would install beta firmware and take a factoury deafult reset. you do not need to change the firewall or things like that to get port NAT to work
set up ip on LAN and WAN
set up Port NAT before making other settings.
this here should not be a hocus pocus to get it to work
clock on the router should have nothing to say.
I still do not think it is the problem with the router, but it is difficult to say, you can tell us in the forum when you find out this :-)
but a full reset to deafult and new firmware is done quickly and test to see if there may be a firmware problem,
all my test is on this firmware above.
Have TP-LINK something to say on this case???
@Fae any suggestion?
@shberge Thank you for your trying to help with this case. I cannot reproduce the problem either.
@LarryMerino For your case, I'd like to escalate to the TP-Link support team who could help you more efficiently.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Once the issue is addressed or resolved, I'd encourage you to share it with the community. Thank you in advance!
- Copy Link
- Report Inappropriate Content
Is there any solution on this case?
I'm curious about what the solution was.
/shberge
- Copy Link
- Report Inappropriate Content
@shberge Hi,
Yes, finally we can find the issue, I will explain the datails, I'm sorry for the delay in reply
It seems that the problem was caused for my ISP
I explain myself better, the packets coming out from my local network are marked by a code called DSCP that is kind of priority code in the packet management of QoS (Quality of service).
The thing is that my ISP are not allowing marked packet with DSCP > 0 and for that reason I had those problems
SOLUTION:
I installed the Omada controller in a virtual machine running Ubuntu (I found some tutorials on youtube on how to do this but in these days I will buy the Omada controller hardware instead) and then I went to: settings -> wired networks -> LAN and I adopted my router with the Omada controller, I had some problems adopting my router but after to do a factory reset to my router and configure my ip's in the same subnet, all went well.
Once his is done, I went to: settings -> wired networks -> Internet, and in the Advanced Settings I set "QoS Tag" as None. And since then, everything works fine.
I want to thank technical support for helping me find the problem and give me a solution.
You are the best!
I hope all of this can be help to anyone who has a similar problem.
Thank you very much again and have a nice day.
Best regards.
- Copy Link
- Report Inappropriate Content
Hi, good that it worked out for you 
. but the settings you refer to I do not find on my controler (OC200), please send me some screenshots so I can identify where this is set, thanks.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 6825
Replies: 14
Voters 0
No one has voted for it yet.