Regular Visitor
•
5 Messages
Re: Sonicwall VPN won't connect via Xfinity
Hello - I've encountered the same issue since yesterday. Disabling the Advance Security didn't work for me. Is there something else that I can try. I've been waiting for Comcast to call me. I can connect using the free wifi but not my personal, secure wifi.
Thank you!
Accepted Solution
anonymous239847
Frequent Visitor
•
5 Messages
5 years ago
Ok, last update. I'm not sure if it even matters to anyone, but in case someone finds this helpful in the future, I'll post anyway. It turns out the issue with slow throughput and frequent drops via Comcast and NetExtender (particularly when using RDP) was a firewall configuration change at my company.
I still don't fully understand why it worked on other ISPs and mobile hotspot without any problems because the SonicWall VPN and Sonicwall Firewall were the same at the company side, but here is the change on the SonicWall firewall that ended up resolving this issue:
Packet capture on the firewall showed drop code 70, invalid TCP flag. We disabled the option to 'Perform SYN validation when not operating in strict TCP compliance mode' and no longer saw dropped packets from your remote address.
0
0
jel20
Regular Visitor
•
5 Messages
5 years ago
Tuesday evening it was finally resolved after the issue was elevated.
The default for these gateways is 10.0.0.1. Change it to 192.xxx.x.x. most VPN's run off of 192. The end user can log into the gateway by putting the 10.0.0.1 address in a web browser on a machine then selecting connection, then local IP and changing it to the 192 address there where it says IPv4 gateway address.
I hope this helps!
0
0
anonymous239847
Frequent Visitor
•
5 Messages
5 years ago
I have been having the same issue as well. Disabling Advanced Threat Protection did not work for me either. I believe it's something specific on the Comcast Router Wifi / WLAN network. I don't seem to have any issues when hard-wiring directly to the modem. Unfortunately, my work space is not close to the router, so I would love to be able to work remotely within my home again.
It's worth noting that I have this issue on the 2.4 and 5 Ghz wireless networks, but as jel20 pointed out, he can use the xfinity wifi with no issues. I have tested from three different laptops with different wireless chipsets (Intel, Broadcom, and Atheros). Updating NIC drivers makes no difference. Friends of mine are having the same issue with Comcast in different areas. Would love to find a resolution to this problem. Since I am forced to work remotely, this is kind of a big deal to me. I don't want to burn through all of my mobile data either, which is currently workaround number two. Someone please advise.
0
0
anonymous239847
Frequent Visitor
•
5 Messages
5 years ago
Hi Jel20,
It's funny you mention that. I had actually changed the LAN subnet a while back thinking that I may have had conflicting routes. My Comcast/Xfinity LAN subnet is 192.168.0.0/24 after changing it from the 10.0.0.1 gateway address. Here are the routes being pushed by SonicWall NetExtender:
10.1.0.0/255.255.0.0
10.50.0.0/255.255.0.0
10.60.0.0/255.255.0.0
172.16.0.0/255.255.0.0
192.168.1.0/255.255.255.0
192.168.2.0/255.255.255.0
Now I am beginning to wonder if we are having different issues entirely. Were you not able to connect at all or was yours behaving erratically like mine after getting connected? I also don't know how this would explain why mine seems to work fine when hardwired vs. wireless. Anyway, thanks for following up!
0
0
anonymous239847
Frequent Visitor
•
5 Messages
5 years ago
Just a quick update. I decided to put my Comcast modem into bridge mode and use my own router (Netgear R6300v2). The LAN subnet on the Netgear appliance was set to 172.16.0.0/24 and unfortunately, still had the same issue. Also now noticing the same problem with a wired connection to the Comcast router. I can use Netextender over the wire for a little while longer before having issues, but ultimately, I wind up in the same situation. It just takes longer to experience the issue when wired, just very strange....
0
0