@brianhendrix - Make sure you are using the most recent firmware. that was an issue with 2.20 (I believe). The updated 2.22 (and 2.21 beta) fixed what you seem to be describing.