Possible Solution to Slingbox Error 0x9236000d on Windows

imageI recently upgraded my old Linksys router to the custom firmware, Tomato (definitely recommend!). (I had been running DD-WRT, which is powerful, but has a much more complex user interface). After upgrading the router, I was unable to connect to my Slingbox. (As an aside, I’m not 100% confident that there’s a cause/effect there – but it’s one key thing that changed recently).

The error was:

Error: 0x9236000d
Context: 20
Operation: 110

The online help suggested that something might be wrong and I should fix it before continuing. Duh.

After experimenting with some firewall settings, IP address changes, and a few more pointless attempts, I found that the only thing that fixed the connectivity issues was to completely reset my Slingbox and run through the setup again. The Sling Player software immediately recognized the “unconfigured” Sllngbox as soon as the reset finished. I reapplied all of the settings (including resetting the passwords back to their old values), and I’m again able to connect and use the Slingbox with no issues.

I hope this helps someone else as there really wasn’t much information about this error anywhere on the Internet.

Field level help — or hindrance?

image

image

I found the technique intriguing, but troubling in implementation. The problem I had in particular the way it completely obscured the content underneath each field (there was help for every field). I would have liked if it had only covered up the fields below the active field with a mostly opaque help box. But, as it was it would cover a field I just entered.

Then, there was the auto tabbing. Stop that. I accidentally tabbed through the month field, and then couldn’t tab BACK into the month field because of broken logic in the “day” field.