Jump to content

Kevin Fulton

Members
  • Content Count

    3
  • Joined

  • Last visited

Everything posted by Kevin Fulton

  1. On multiple PCs (Surface Pro 4, Asus UX32VD) that I have running Windows 10 insider preview build 14393 (which will be released to the general public as the Anniversary update very soon), if Enpass Desktop is running (tested with versions 5.2.1 and 5.2.3), it causes cyclic network delays on wireless networks. Every 8-10 seconds, ping times over wireless are greatly increased for 1-3 seconds, and throughput drops to near nothing. For example, if Enpass is not running, I get between 27-29ms latency when I ping Google DNS. As soon as I launch Enpass Desktop, this is what I get: Reply from 8.8.8.8: bytes=32 time=332ms TTL=41 Reply from 8.8.8.8: bytes=32 time=287ms TTL=41 Reply from 8.8.8.8: bytes=32 time=320ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=74ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=28ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=158ms TTL=41 Reply from 8.8.8.8: bytes=32 time=94ms TTL=41 Reply from 8.8.8.8: bytes=32 time=111ms TTL=41 Reply from 8.8.8.8: bytes=32 time=294ms TTL=41 Reply from 8.8.8.8: bytes=32 time=358ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=28ms TTL=41 Reply from 8.8.8.8: bytes=32 time=349ms TTL=41 Reply from 8.8.8.8: bytes=32 time=474ms TTL=41 Reply from 8.8.8.8: bytes=32 time=85ms TTL=41 Reply from 8.8.8.8: bytes=32 time=146ms TTL=41 Reply from 8.8.8.8: bytes=32 time=28ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=28ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=236ms TTL=41 Reply from 8.8.8.8: bytes=32 time=125ms TTL=41 Reply from 8.8.8.8: bytes=32 time=280ms TTL=41 Reply from 8.8.8.8: bytes=32 time=449ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=432ms TTL=41 Reply from 8.8.8.8: bytes=32 time=40ms TTL=41 Reply from 8.8.8.8: bytes=32 time=226ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 As soon as Enpass is closed, the problem stops and ping times return to normal. This is not just a cosmetic issue. Throughput speeds greatly decrease or hit 0, as tested by speedtest.net, iperf, and the Windows file copy dialog. This problem does not happen when running the UWP Enpass from the Windows Store, only the desktop version. It also does not happen on a wired network connection. It took me quite a while to figure out that Enpass was causing my network problems. I really love the Desktop version and would hate to have to stop using it. Any suggestions would be appreciated! Thanks
×
×
  • Create New...