Menu

Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Sign In Register

Connection up and down once connected to VPN

DDRDieselDDRDiesel Newbie ✭
edited June 2020 in Mid Range Firewalls

We've recently run into an issue with the VPN set up on our NSA 2650.  At times, when a user connects, they get a constant up/down connection like a sawtooth pattern.  When they disconnect from the VPN, their internet connection is completely fine and a ping -t shows no drops whatsoever.  But once they connect, this is their ping result:


C:\WINDOWS\system32>ping *redacted* -t

Pinging *redacted* [131.*.*.*] with 32 bytes of data:

Reply from 131.*.*.*: bytes=32 time=17ms TTL=64

Reply from 131.*.*.*: bytes=32 time=18ms TTL=64

Reply from 131.*.*.*: bytes=32 time=20ms TTL=64

Reply from 131.*.*.*: bytes=32 time=17ms TTL=64

Reply from 131.*.*.*: bytes=32 time=24ms TTL=64

Reply from 131.*.*.*: bytes=32 time=17ms TTL=64

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 131.*.*.*: bytes=32 time=24ms TTL=64

Reply from 131.*.*.*: bytes=32 time=24ms TTL=64

Reply from 131.*.*.*: bytes=32 time=17ms TTL=64

Reply from 131.*.*.*: bytes=32 time=17ms TTL=64

Reply from 131.*.*.*: bytes=32 time=31ms TTL=64

Reply from 131.*.*.*: bytes=32 time=19ms TTL=64

Reply from 131.*.*.*: bytes=32 time=19ms TTL=64

Reply from 131.*.*.*: bytes=32 time=20ms TTL=64

Reply from 131.*.*.*: bytes=32 time=23ms TTL=64

Reply from 131.*.*.*: bytes=32 time=17ms TTL=64

Reply from 131.*.*.*: bytes=32 time=23ms TTL=64

Reply from 131.*.*.*: bytes=32 time=17ms TTL=64

Reply from 131.*.*.*: bytes=32 time=23ms TTL=64

Reply from 131.*.*.*: bytes=32 time=18ms TTL=64

Reply from 131.*.*.*: bytes=32 time=19ms TTL=64

Reply from 131.*.*.*: bytes=32 time=15ms TTL=64

Reply from 131.*.*.*: bytes=32 time=23ms TTL=64

Reply from 131.*.*.*: bytes=32 time=24ms TTL=64

Reply from 131.*.*.*: bytes=32 time=16ms TTL=64

Reply from 131.*.*.*: bytes=32 time=16ms TTL=64

Reply from 131.*.*.*: bytes=32 time=25ms TTL=64

Reply from 131.*.*.*: bytes=32 time=21ms TTL=64

Reply from 131.*.*.*: bytes=32 time=19ms TTL=64

Reply from 131.*.*.*: bytes=32 time=25ms TTL=64

Reply from 131.*.*.*: bytes=32 time=16ms TTL=64

Reply from 131.*.*.*: bytes=32 time=20ms TTL=64

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 131.*.*.*: bytes=32 time=24ms TTL=64

Reply from 131.*.*.*: bytes=32 time=18ms TTL=64

Reply from 131.*.*.*: bytes=32 time=20ms TTL=64

Reply from 131.*.*.*: bytes=32 time=19ms TTL=64

Reply from 131.*.*.*: bytes=32 time=20ms TTL=64

Reply from 131.*.*.*: bytes=32 time=18ms TTL=64

Reply from 131.*.*.*: bytes=32 time=32ms TTL=64

Reply from 131.*.*.*: bytes=32 time=15ms TTL=64

Ping statistics for 131.*.*.*:

   Packets: Sent = 54, Received = 40, Lost = 14 (25% loss),

Approximate round trip times in milli-seconds:

   Minimum = 15ms, Maximum = 32ms, Average = 20ms

*Note that this is only a small sample, but it's this exact pattern over and over.  Each dropped packet is a time of about ~3 seconds, whereas the returned pings are just under 1 second each.  So it's an equivalent time of up and down connection


Not sure what would be causing this, and most users don't seem to have this issue at all.  The users that are affected have all different setups regarding to how they connect to the internet.  Some are wireless, others are wired.  Desktop, laptop, tablet, different ISP, but always this issue.  Is this something on the SonicWall that has to be configured?  Hoping someone else has run into this at least once and can provide me some direction

Category: Mid Range Firewalls
Reply
Tagged:

Answers

Sign In or Register to comment.