Skip to main content

Allowing WeChat to Sign Up and to get QR Code for login in SonicWall

By
SonicWall's Application Control block some required Application for WeChat Application.

So that Mobile Device users using WeChat will not be able to Sign Up in you network and they will get "Connection error. Check your network settings."


For those who already has account also will not able to sign in by using QR code.

Laptop/Desktop WeChat user also will encounter the error as below.



To solve these issue, you need to Unblock/Allow the Applications from below Application Signature List in your SonicWall.
Application Category : Proxy-Access (27)
Application : Proxy-Access HTTP (966)
Application Signature : Proxy-Access HTTP Proxy -- HTTP Proxy POST (9685)

You still need to Allow/Exclude below IP Address lists from Application Control List of your SonicWall.(In fact, WeChat used many IP Addresses and need to check logs and add some more if your issue not resolve yet by adding below list.)
203.205.129.101
203.205.147.168
203.205.151.160
140.206.160.213

Once you done above steps, your users shouldn't be any issue when they using WeChat either on their Mobile Devices or Laptop/Desktop within your network.
(For me I really do not want to allow for this application as it is not secure but have to allow because of business need. So I have to monitor closely on usage of this application.)

Have a good time.
(Be knowledgeable, pass it on then)

Labels:

Comments

  1. sompii123September 27, 2020 at 11:22 PM

    help

    ReplyDelete
  2. uniqueaimincJanuary 1, 2022 at 10:53 AM

    I have been searching for such an informative post for many days and it seems my search just ended here. good work. keep posting. If you want to get Information about Online Payment In China visit our website.

    ReplyDelete

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...
7 comments
Read more