WHY DOES L2TP WORK AT THE OFFICE BUT NOT FROM A HOTEL?

Solveddnsroutingvpn4 replies 路 227 views 路 started

Accepted solution

by LucaJump to the reply

hotel and guest networks sometimes block UDP or specific ports. if the client claims connected but no handshake data flows, try the TCP/443 fallback mode if your VPN offers one.

  1. Weird one :/ From a hotel, L2TP connects and then nothing internal resolves:

    if I type the IP address of teh RDP server directly it sometimes works! but names fail every time. help me before I start memorizing IP addresses.

    i've also flushed the DNS cache, rebooted my laptop and tried a different browser, just in case. no change. i'm convinced it's something about how names are looked up over L2TP, but idk where to look.

    4
  2. for split tunnel setups, teh internal subnets must be in the pushed routes (AllowedIPs in WireGuard, push "route ..." in OpenVPN). if the RDP server lives in a subnet not in that list, it goes out ur normal internet connection instead. worked for me anyway 馃し

    4 0 helpful
  3. Accepted solution

    hotel and guest networks sometimes block UDP or specific ports. if the client claims connected but no handshake data flows, try the TCP/443 fallback mode if your VPN offers one.

    1 5 helpful
  4. Id move teh corporate network off common home ranges entirely. Its painful once, then the overlap problem is gone for everyone.

    1 0 helpful
  5. @framemonk dude changed my home router to a different subnet... evreything works over L2TP now. overlap was the culprit.

    1 2 helpful

Reply to this topic

Sign in or create an account to reply.