Basic Smoked Beef Jerky

I love beef jerky, but it can get quite expensive.  If your only experience with this lovely creation is from the little tiny plastic bags at the grocery store then you have done yourself a disservice! 

The typical homemade Smoked Beef Jerky Recipe calls for the beef to be marinated in artificial smoke to get all of its smoked flavor. It is then placed in a dehydrator for several hours until dry.  That’s heads and shoulders above the store bought plastic they pass off for jerky these days, but we can do better (Yes we can!).  Never, ever trust any packaging that says “Natural Style*” with an asterisk.



smoked beef jerky recipe


To be authentic, a smoked beef jerky recipe should use a smoker.  Now some would argue that charcoal is the only way to go – I’m not going to debate charcoal vs. electric here, but lets just say I use the electric.  That being said, the smoker is the only way to get that classic and "true" smoky taste that is desired.

The smoked beef jerky recipe dried outside on a smoker is a little closer to the old cowboy jerky. That’s when beef was cured and dried to preserve for eating on the long trails. It is naturally preserved instead of loaded with preservatives.

I’ve been playing around with different variations of this basic recipe for years, every time the supermarkets would have a sale on beef I would grab a few pounds.  here’s what to start with:

Homemade Beef Jerky


  • 2-3 pounds steak/roast/london broil (whatever is on sale), cut into 1/4 inch thick slices
  • 1 cup soy sauce
  • 1/2 cup Worcestershire sauce
  • 1/4 cup cider vinegar (white wine vinegar works too)
  • 1/4 cup brown sugar

In a large bowl or Ziploc bag, combine everything.  Cover and refrigerate overnight.

Prepare an outdoor smoker for low heat and lightly oil grate.

Lay the meat out on the grill so that the strips do not touch. Smoke over the lowest heat on your smoker.  Beef jerky will be done when the edges appear dry with just a tiny bit of moisture in the middle of the pieces of meat, or about 6-8 hours.  After your first bite you’ll never go back to store bought jerky again.  You’re welcome!

SharePoint–Disable LoopBack Check

A while ago Microsoft released a “fix” that caused issues with NTLM authentication issues when you try to access a server locally.  This is because Microsoft has created a new security feature called the loopback check and by default the value of the DisableLoopbackCeck registry value is set to 0.  Most of the posts I’ve read will say to set the value to 1 with the standard “but Microsoft does not recommend this for production”. 

The registry value you need to change is located here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

LSA stands for the “Local Security Authority”.  Rather thank just disabling the loopback, you can run the following method to get rid of the annoying pop-up when locally accessing the resources from the server:

Method 1 : Create the Local Security Authority host names that can be referenced in an NTLM authentication request

To do this, follow these steps for all the nodes on the client computer:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  3. Right-click MSV1_0, point to New, and then click Multi-String Value.
  4. In the Name column, type BackConnectionHostNames, and then press ENTER.
  5. Right-click BackConnectionHostNames, and then click Modify.
  6. In the Value data box, type the CNAME or the DNS alias, that is used for the local shares on the computer, and then click OK.
    Note Type each host name on a separate line.
    Note If the BackConnectionHostNames registry entry exists as a REG_DWORD type, you have to delete the BackConnectionHostNames registry entry.
  7. Exit Registry Editor, and then restart the computer.

However, if you want to kill the fly with a sledgehammer and don’t want to have to deal with iterating through/typing all of the BackConnectionHostNames, there’s always the tried and true method of just turning the darn thing off:

Method 2: Disable the authentication loopback check

Re-enable the behavior by setting the DisableLoopbackCheck registry entry in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry subkey to 1. To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.
  8. Restart the computer.

Method 3: Disable the authentication loopback check with PowerShell

  1. Open a Powershell console and enter the following:
    New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" –PropertyType dword
  2. Restart the computer.

However, realize that this is a bad idea on production systems because the NTLM reflection protection is part of a fix for the SMB vulnerability.  This problem occurs because of the way that NT LAN Manager (NTLM) treats different naming conventions as remote entities instead of as local entities. A local authentication failure might occur when the client calculates and caches the correct response to the NTLM challenge that is sent by the server in local "lsass" memory before the response is sent back to the server. When the server code for NTLM finds the received response in the local "lsass" cache, the code does not honor the authentication request and treats it as a replay attack. This behavior leads to a local authentication failure.  Disabling NTLM reflection protection on an affected system will return the system to a vulnerable state for the particular SPN for which the reflection protection was disabled.

Remember: If you turn off the loopback check you are leaving your server or SPN open to a replay attack and could allow remote code execution.