MR200 vpn issues

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

MR200 vpn issues

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
MR200 vpn issues
MR200 vpn issues
2018-09-24 23:27:27
Model : Hardware Version : Firmware Version : ISP : Hi. My daughter just moved from Norway to Sweden, and I set her up with an MR200 router. It works OK for normal use, but when she connects to the VPN server in my router, she can not see the NAS. If she bypasses the MR200 she can connect, so the issue seems to be there. I will visit her next week and hope that someone here can help me resolve the issue. Best, Haavar
  0      
  0      
#1
Options
2 Reply
Re:MR200 vpn issues
2018-10-02 15:09:42
I have a same issue. vpn ipsec passtrough not work. If you use latest firmware 0.9.1 1.2 v004a.0 Build 180502 Rel.53881n ipsec passtrough not work at all.
If you use some earlier beta version. Ipsec passtrough work somehow unstable. It falls down often. I had written to tplink support center. No answer.

So today only solution what somehow worked for me is with beta firmware. See the link below https://forum.tp-link.com/showthread.php?94393-problem-with-vpn-passthrough-in-Archer-MR200
Archer MR200 v1 I think hardware is ok but firmware development to this model is pretty weak.
  0  
  0  
#2
Options
Re:MR200 vpn issues
2018-10-08 19:49:49
First the issue is regarding an MR400 V1 EU - not MR200 - my mistake.

I discovered when in VPN, via the MR400 to my home VPN server/router, one could only see the MR400 NW infrastructure on the Client. I do not know why, but perhaps the MR400 should use my home router as DNS.

I then realized that my home router and the MR400 shared the same IP adress (DNS-issue?). Setting the IP for the MR400 to 192.168.0.1 resolved this.
I can now Access the NAS on my home NW (via the MR400), but Windows/mac will not willingly display these recourses in the file manager (DNS???).

As many mobile nw Suppliers no longer offers you a Public IP for Your router, I set a specific APN to Ensure this. Unfortunately i did not verify the MR400 "public" IP before I made the change, som Im not shure if this is relevant here.

Conclusion: Both my routers had the same IP - not good. Cause may be DNS issues. Resolving this in one way or another should fix the problem.
  0  
  0  
#3
Options

Information

Helpful: 0

Views: 1408

Replies: 2

Related Articles