Revision as of 15:15, 9 March 2022 edit Argymeg (talk \| contribs) 275 edits m Fix dead link Tag: Visual edit ← Previous edit		Revision as of 20:30, 22 March 2022 edit undo Bender the Bot (talk \| contribs) Bots 1,064,377 edits m →top: HTTP to HTTPS for Wayback Machine, replaced: http://web.archive.org/ → https://web.archive.org/ Tag: AWB Next edit →
Line 32: \| accessdate=2015-10-17}}</ref> SSTP was intended only for remote client access, it generally does not support site-to-site VPN tunnels.<ref>{{cite web \|last=Jain \|first=Samir \|date=2007-01-10 \|title=SSTP FAQ - Part 1: Generic \|url=http://blogs.technet.com/b/rrasblog/archive/2007/01/10/sstp-faq-part-1-generic.aspx \|url-status=dead \|archive-url=~~http~~https://web.archive.org/web/20101012205841/http://blogs.technet.com/b/rrasblog/archive/2007/01/10/sstp-faq-part-1-generic.aspx \|archive-date=2010-10-12 \|website=TechNet Blogs \|accessdate=}}</ref> SSTP suffers from the same performance limitations as any other IP-over-TCP tunnel. In general, performance will be acceptable only as long as there is sufficient excess bandwidth on the un-tunneled network link to guarantee that the tunneled TCP timers do not expire. If this becomes untrue, performance falls off dramatically. This is known as the "TCP meltdown problem".<ref>{{cite web

Secure Socket Tunneling Protocol: Difference between revisions