Mac OS clients using Microsoft Remote Desktop are unable to connect via Remote Desktop Gateway Servers

Over the summer we build a Remote Desktop Gateway Cluster to provide remote access to workstations for some of our clients.

Initial testing worked great for Mac OS, Windows and Linux users. For Mac OS we had clients download the official Microsoft RDP App from the App Store.

Right before go-live day we updated our RDP template we provide to clients and that’s when things started going wrong for only Mac users…. and only some Mac users.

Clients using Mac OS 10.15.x and Microsoft RDP 1.14.x were greeted with this error message:

Unable to connect

We couldn’t connect to the Remote PC. This might be due to an expired password. If this keeps happening, contact your network administrator for assistance.

Error code: 0x207

I originally came cross this Technet thread when researching the issue:

Turns out that didn’t apply to us. The registry entries it mentioned did not exist on our servers.

We found that rolling back the Microsoft RDP Client to 1.13.8 (the latest 1.13.x build) would solve the problem.

We also found that the latest Microsoft RDP Client, 1.14.0, worked fine on Mac OS 10.14.1 but the same was not true for Mac OS 10.15.6.

On a whim one of our Techs still had a copy of our original RDP template we used for initial testing where everything worked and found that it still worked on Mac OS 10.15.6 with Microsoft RDP 1.14.0.

We cracked open the RDP file (it’s just text) to find what the difference was:

We had added the following line:


In an attempt to make it easier for clients to connect by auto-populating our domain name into the shortcut.

When we removed this line from our template the problem went away.

OctoPrint Firmware Updater plugin settings for Creality CR-10 V3

Just wanted to post my settings for this plugin to save others time. I took me a little bit before I found working settings by combing through multiple forums/comment sections.

  • Flash Method: avrdude (Atmel AVR Family)
  • AVR MCU: ATmega2560
  • Path to avrdude: <Your path, you can easily find this by typing “which avrdude”  when logged into your OctoPrint via SSH. If the command is not found run “sudo apt-get install avrdude” to install avrdude then re-run “which avrdude”>
  • AVR Programmer Type: wiring

I left everything else default and am able to load firmware without issue.

Firmware Plugin Settings


I’ve also added some post-flash configuration

These gcodes do the following after a flash:

M502; Factory reset your printer
M851 Z-2.630; Set Z Probe Offset (mine is -2.630mm, yours will likely be different)
M500; Save settings
M501; Load settings


Marlin 2.x for a CR-10 V3

I’ve been wanting a 3D printer for a while and finally bought one. I ended up with a Creality CR-10 V3 based on a friends recommendation.

CR-10 V3

I added a BL Touch v3.1 to it and then, instead of using the Creality provided firmware based on Marlin 1.1.6 that still says “CR-10 V2” all over it, I built Marlin 2.0.6 for it with a lot of help from some friends.

Here’s my original Reddit post:

Here are my configuration files and some pre-compiled firmware if you want to use it “as is” and not have to build your own:

I’ve just completed a print and appears to have worked just fine so I think this firmware works.

Replacing the battery in Balanzza Mini Rechargeable Scale

After my last trip to Mexico I had the desire to buy a rechargeable luggage scale so I didn’t have to remember to replace the batteries in it. When we travel we always have multiple USB chargers with us so a rechargeable luggage scale made a lot of sense. Based on the Wirecutters recommendation I looked to pickup a Balanzza Mini Rechargeable Scale (non-referral link).

I live in Canada and couldn’t find a local supplier and most online retailers in the US would have charged an arm and a leg on shipping or simply had no stock so I turned to eBay and found someone selling one, brand new condition, for a reasonable price.

I placed my order and waited the 2-3 weeks to arrive and when it finally got here it wouldn’t not power on. I figured the battery was dead and plugged it in to charge. After about 8 hours charging the charge light hadn’t switched from red to green. I was able to power on the scale and it worked until I disconnected it from the USB charging cable, then it died again. Seemed like either the charging component wasn’t working properly or the battery inside the scale was toast or had a bad connection.

The unit was brand new and in a sealed package so I didn’t feel like I’d been duped. I reached out to Balanzza support and heard nothing back after multiple attempts to contact them. Since I had nothing to lose at this point I decided to crack it open.

Sorry I didn’t take good photos of the inside initially, don’t know why:

Looks like the scale comes with a 100mAh LiPol battery (601522). These are easy enough to find on Amazon, eBay and Alibaba depending on how much money you want to trade off for time waiting for the battery to arrive.

I had some 240mAh LiPol’s lying around for a small quad copter drone so I figured I’d do a quick test with one of those to try and determine if the issue was the battery.

Very promising. This confirmed the included battery had no charge and was either toast OR the charging controller was faulty… or both. I cracked out the multi-meter and checked the 100mAh battery and it was toast, or at least toast looking enough I wasn’t going to bother trying to charge it. I also didn’t have a good way to charge it.

Space is tight inside the Balanzza and the original battery sat on the right side of the device in a very small space. Over on the left side of the scale there is a nice cavity that gave me a bit more wiggle room to put a bigger battery in but it was still too small to fit one of my 240mAh LiPols in so I was going to have to order something. Since I had to buy new batteries anyway I tried to find the biggest mAh LiPol that would fit inside the cavity on the left side of the Balanzza and came up with the 150mAh LiPol (402020) which measured 2.0cm*2.0cm*0.4 cm and would fit nicely. It seemed battery larger than that, mAh wise, was too physically large to fit.

Some quick soldering and shrink tube later:

and I ended up with a functioning scale. I also tested charging and after 1-2 hours the light went from red to green. Appears I fixed it and gained 50% more battery capacity!

SolarWinds Web Helpdesk 12.7.2 post-upgrade problems

Recently after upgrading our WHD from 12.7.1 to 12.7.2 we started experiencing two issues that turned out to be related.

Adding comments to tickets could generate an error stating: “Something went wrong. Please contact SolarWinds support for assitance or review the Web Hep Desk logs.”

and when trying to upload attachments to tickets: “Your upload failed: Connection reset by peer: Amount read didn’t match content-length”

After some back and forth with SolarWinds support they said the issue is related to the version of Tomcat they bundled with WHD 12.7.2. The bundled version is 9.0.31 and SolarWinds recommends manually upgrading it to 9.0.34 to fix the issue.

The procedure I followed was:

# Login to your WHD server and become root

# Make a temp directory, go into it and download Tomcat 9.0.34
mkdir temp
cd temp
wget -c

# Stop WHD
service stop webhelpdesk

# Backup your existing WHD Tomcat directory just in case
cd /usr/local/webhelpdesk/bin
tar -cf tomcatBackup-20200423.tar tomcat
gzip -9 tomcatBackup-20200423.tar

# Copy Tomcat 9.0.34 overtop of Tomcat 9.0.31 while preserving WHD related content
cd ~/temp
cd apache-tomcat-9.0.34
cp -Raf bin conf lib NOTICE RELEASE-NOTES /usr/local/webhelpdesk/bin/tomcat/

# Reboot your server or manually start WHD back up
shutdown -r now
# OR
service webhelpdesk start

Once we did this the errors above went away.