ufgroup.blogg.se - Sonicwall netextender server is not reachable

To allow outside clients to connect to our Wildfire server without having to run a VPN client we can open port 5222 and Spark will connect using TLS. SSL/TLS is often used in one breath so I wasn’‘t really aware of the differences before flogging this problem to death but they ain’‘t the same and although Wildfire supports both, Spark does not anymore. As of Spark 2.0, Spark no longer uses SSL but uses its more advanced but less prevalent cousin TLS. We’‘re using Wildfire 3.01 behind a firewall as an internal chat server but we have been allowing server to server connections, have the pyAIMt gateway installed and working, and were allowing SSL client connections also through the firewall. I’‘ll share what we learned here and with any luck it will help some other folks out there. So, I consider this problem with jvm flag settings on the serverĬharley and I worked extensively on this today to undestand it in our environment. I restarted the server and I didn’'t had this problem anymore.Īlso, there was this file stderr.log on the server with the following content:Įxception in thread “Thread-5” : Java heap spaceĮxception in thread “AWT-EventQueue-0” : Java heap space

At the time of problem the memory usage was 75,716 KB Similarly, Wildfired.exe process at startup uses: 43,772 KB. At the time of problem the memory usage was 88,176 KB. Wildfire.exe process at startup uses: 11,644 KB. So I realized that the problem is with the server and not client. I noticed that the client is showing Invalid Username / password error when the server is not responding after waiting for certain time. To understand the problem, I ran the Spark application from my MyEclipse IDE. Has anyone experienced this? Any idea why a new SSL cert would cause these issues all of a sudden? Any advice that can be provided would be appreciated. If we have those same users connect instead to their phone/tablet hotspot, VPN works fine.

One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server!Īfter a bit of troubleshooting, we found that the only users that were having problems were those that were connected to a site that was using Spectrum as their ISP.

Please make sure the server has a valid certificate setup.

SSL error happened, your OS may not support connecting to the server.

The server may be down or your internet settings may be down. They received one or more of the following errors:

At this point, we started hearing from some of our users that they could no longer connect to the VPN. Everything has been working great for the last year since we installed this device but the SSL cert that we use for VPN connections recently expired so I had to remove the existing one and install the new one. We use an NSA 4700 at our corporate HQ and all user computers are configured to use the NetExtender VPN client to connect to the office when needed.