Dell SonicWall Site-To-Site VPN Blocking Ping

Found my answer here:

“You may already know this but just in case, if you would prefer to keep your low priority IPS enabled but still allow ICMP traffic, that is possible.  Under the IPS Policies section, you can set the category drop-down for ICMP and then click the pencil icon.  Once you do that, set the Prevention drop-down to Disable and then click OK.  That should let ICMP traffic work while still keeping IPS enabled for other types of low priority traffic.

Because it’s all ICMP, it will also allow other things like traceroute to function.  I played around with some of the granular controls but I couldn’t find a way to allow just ICMP Ping and Reply so this seems to be the next best thing.” -Daniel Bruss

“The blanket VPN > LAN rule may not be sufficient.  The new SonicWALL’s interfaces are sometimes protected separately.  Try creating a separate rule specifically to allow ping from the VPN to that interface, e.g. Allow PING from VPN > LAN on X0 interface IP (or whatever the relevant interface IP is).  I had to do this recently to get the ping to work across the VPN.” – BecauseI’mGood

Windows File Recovery Get Button Not Working

Attempting to install Windows File Recovery application from the Microsoft Store by clicking the Get button failed with no explanation. It just had a blue get button that remained there regardless of how many times you click it or closing and reopening the store app.

If you’re like me you ran the “wsreset” command just to make sure that there was nothing wrong with the store itself.

What I had discovered though that since this was a recent feature in Windows 10 that the device I was attempting to use it on was a version previous to 2004.

Updating to a version 2004 or later resolved the issue.

To check which version of Windows that you are running, press the windows key, and begin typing “winver”, then press enter.

This will show your version number.

LOC SMS Suite Error: SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]

Ensure that the network connection profile is set to Private or Domain. If set to public, communication with registers will fail as SMB shares are used to transfer data between the Point-Of-Sale (POS) devices and the Store Management Suite (SMS) server.

An easy way to check this is by opening an elevated powershell window and entering the following command:

PS> Get-NetConnectionProfile

This will list all of the network connection’s profiles. To ensure which profile is associated with which network interface card (NIC) use the following command to cross-reference the variable “InterfaceIndex” with “ifIndex”

PS> Get-NetAdapter

Once, you have identified the NIC that you want to change the connection profile of from Public to Private you can set the connection using this command:

PS> Set-NetConnectionProfile -InterfaceIndex <number> -NetworkCategory Private

Changing “Private” to “Domain” will change the network connection profile to domain.

Connecting Azure to On-Premise Network

There are essentially 2 ways that I’ve discovered so far. The first one that anyone is going to do is to use the Azure VPN Gateway. That’s what it says in all of the documentation online. Except, it doesn’t say that here:,use%20from%20the%20dropdown.%20…%20More%20items…%20

It’s called something else. It’s the same thing, different name. That caused me a lot of headache and wasted time. It’s called a “Virtual Network Gateway”. So, when you search for “VPN Gateway” in the Azure portal this is why it turns up with no results.

Here are some of the main ingredients needed:

So, you have your on-premise equipment and your “cloud equipment” is what I’m going to call it.

For example, based on this source: I’m going to discuss the route-based VPN example.

It will look a lot like this:

Pihole on Docker Guide

Here is the best one that I have found so far:

docker pull pihole/pihole

Then create and start the container

docker run -d --name pihole -e ServerIP= -e WEBPASSWORD=password -e TZ=America/Chicago -e DNS1= -e DNS2= -e DNS3= -p 80:80 -p 53:53/tcp -p 53:53/udp -p 443:443 --restart=unless-stopped pihole/pihole:latest