We've seen this so many times, & getting the user to believe it is fun as well.ġ) tell them to use wired connections if possibleĢ) Have a dig through the event logs, there are a couple of events that show up if they loose the physical connection (99% of the problems in my experience) - Event ID 15500 under Microsoft-Windows-Wired-AutoConfig/Operational (wired connection) or ID 8003 under Microsoft-Windows-WLAN-AutoConfig/Operational (wifi), for some of our users who didn't believe us we actually set a scheduled task to trigger on these events that then ran some diagnostics & pinged a message on screen. We cannot figure out a pattern to who has issues vs who does not. It also seems that users are having more luck plugged directly into their router rather than using WIFI but we have many users with the same router connected through WIFI with no issue. Is there any settings we can change in the Sonicwall to help improve stability? I have already decreased the WAN interface MTU to 1350 which helped users connecting via a Verizon hot spot. The users with issues are spread across 2-3 different ISPs so it is not ISP specific. Some users have a good connection one day and can't connect the next. Certain people have rock solid connectivity for weeks/months with no issues. It seems to be linked to their home internet connections.
They either cannot connect or will be connected for a few minutes then lose connectivity. About 25% of our users are having stability issues with the VPN. Each are set up with the WAN group VPN with users accessing via the Global VPN Client. Most of this info is available in the Sonicwall Global VPN Client 4.2 Administrator's Guide, but they don't tell you all this detail and examples.We have at 2 locations. I use Altiris Deployment to run that command on my clients, but any installer will do it, such as KBOX, LANDesk, Microsoft System Center, etc. If you're not familiar with the msiexec command, you can run msiexec /? from a command line and get the swithes, or you can google it. I then created my installation command to send to my clients: msiexec /i \\server\share\sonicwall\GVCInstall64.msi /qb This command says to execute the GVCInstall64.msi in that share, and the /qb says quiet and basic interface. By putting that file into the same folder as the GVCInstall64.msi, the installer will grab that file and put into C:\Program Files\SonicWALL\SonicWALL Global VPN Client on your clients for you.Ħ. I put that default.rcf file also into \\server\share\sonicwall folder. Previously I had created a custom default.rcf file that has all the configurations for my clients.
I then copied only the GVCInstall64.msi to a network share called \\server\share\sonicwallĥ. Extract the file into an MSI with this command: 184-001457-00_Rev_A_GVCSetup64.exe /c /t:C:\temp\sonicwall This will create files called GVCInstall64.msi and RunMSI.exe in the c:\temp\sonicwall folderĤ. I put the file into the following directory on my computer: C:\temp\sonicwallģ. The file will be called something like 184-001457-00_Rev_A_GVCSetup64.exeĢ.
#Sonicwall vpn setup with global vpn client windows 7
Have only tested all of the above on Windows 7 64-bit, but I'm sure the 32-bit works the same.ġ. Msiexec /i \\server\share\GVCInstall64.msi /qb /forcerestart Without it the above commands don't restart the client, and the client seems to work fine.
I have tried it both with and without adding /forcerestart. Msiexec /i \\server\share\GVCInstall64.msi /qb I have also successfully pushed a job to my client with the source files being on a network share: Automates the installation of Global VPN Client (GVC) 4.2.6.
0 kommentar(er)
