<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog — Maurice Sobiera</title>
    <link>https://maurice.sobiera.com/en/blog/</link>
    <atom:link href="https://maurice.sobiera.com/en/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <description>Short versions of the IT case studies from BitBlade Solutions — faults, migrations and security incidents from practice, each linking to the full article.</description>
    <language>en-GB</language>
    <copyright>© 2026 Maurice Sobiera</copyright>
    <generator>hand-written</generator>

    <!-- Die Beitraege liegen auf solutions.bitblade.io; <link> und <guid> zeigen dorthin. -->

    <item>
      <title>Two access points, two networks: why a PC lost its connection when roaming</title>
      <link>https://solutions.bitblade.io/blog/wlan-roaming-native-vlan-switchport/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/wlan-roaming-native-vlan-switchport/en/</guid>
      <pubDate>Sun, 27 Sep 2026 08:00:00 +0200</pubDate>
      <description>Same SSID, two VLANs: why a machine with a static IP fell out of the practice network every time it roamed.</description>
    </item>
    <item>
      <title>New IT for a dental practice: what a complete move really costs in time</title>
      <link>https://solutions.bitblade.io/blog/praxis-it-umzug-was-zeit-kostet/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/praxis-it-umzug-was-zeit-kostet/en/</guid>
      <pubDate>Sun, 27 Sep 2026 08:00:00 +0200</pubDate>
      <description>Five treatment rooms, a new server, a new network: a review of a complete overhaul and where the time actually goes.</description>
    </item>
    <item>
      <title>KIM after a PC replacement: four causes one after another</title>
      <link>https://solutions.bitblade.io/blog/kim-clientmodul-nach-pc-tausch/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/kim-clientmodul-nach-pc-tausch/en/</guid>
      <pubDate>Sun, 27 Sep 2026 08:00:00 +0200</pubDate>
      <description>Wrong host, missing DNS forwarding, missing connector configuration, missing certificate — four causes, resolved one layer at a time.</description>
    </item>
    <item>
      <title>“Connection to the server lost”: when the front-desk PC simply goes to sleep</title>
      <link>https://solutions.bitblade.io/blog/standby-netzwerkkarte-verbindungsabbrueche/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/standby-netzwerkkarte-verbindungsabbrueche/en/</guid>
      <pubDate>Sun, 27 Sep 2026 08:00:00 +0200</pubDate>
      <description>Standby and the network card's power management drop the database connection — three settings that belong on every practice workstation.</description>
    </item>
    <item>
      <title>The browser keeps serving the old version</title>
      <link>https://solutions.bitblade.io/blog/browser-cache-versionscheck-statische-tools/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/browser-cache-versionscheck-statische-tools/en/</guid>
      <pubDate>Mon, 21 Sep 2026 08:00:00 +0200</pubDate>
      <description>An updated web tool stays weeks out of date on the user's machine — why heuristic caching causes it, and how a version check reloads without touching stored data.</description>
    </item>
    <item>
      <title>The phone system only works partially</title>
      <link>https://solutions.bitblade.io/blog/ddos-malware-hinter-3cx-telefonausfall/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/ddos-malware-hinter-3cx-telefonausfall/en/</guid>
      <pubDate>Thu, 10 Sep 2026 08:00:00 +0200</pubDate>
      <description>A forensic case study: a 3CX system appeared broken, but the server beneath it had run DDoS malware unnoticed for seventeen days — four theories, one real culprit.</description>
    </item>
    <item>
      <title>When the trunk isn't broken, it's cancelled</title>
      <link>https://solutions.bitblade.io/blog/3cx-trunk-gekuendigt-routing-fehler/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/3cx-trunk-gekuendigt-routing-fehler/en/</guid>
      <pubDate>Wed, 09 Sep 2026 08:00:00 +0200</pubDate>
      <description>3CX case study: a cancelled SIP trunk and three routing rules without fallback disabled a customer's Switzerland connectivity for months.</description>
    </item>
    <item>
      <title>Keeping ISDN running on a Stiegeler fibre connection</title>
      <link>https://solutions.bitblade.io/blog/isdn-am-glasfaseranschluss/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/isdn-am-glasfaseranschluss/en/</guid>
      <pubDate>Wed, 09 Sep 2026 08:00:00 +0200</pubDate>
      <description>When switching to a fibre connection (FTTH), the legacy ISDN system loses its line. A used FRITZ!Box 7590 behind the provider's router solves it — with three caveats.</description>
    </item>
    <item>
      <title>One click in user management — and four evenings of troubleshooting</title>
      <link>https://solutions.bitblade.io/blog/kennwort-reset-dpapi-masterkey/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/kennwort-reset-dpapi-masterkey/en/</guid>
      <pubDate>Wed, 09 Sep 2026 08:00:00 +0200</pubDate>
      <description>Why an administrator-reset Windows password irrevocably destroys the DPAPI key chain — and a user profile had to be rebuilt from scratch.</description>
    </item>
    <item>
      <title>When a plugin refuses to register: the real reason behind MSI error 1603</title>
      <link>https://solutions.bitblade.io/blog/msi-1603-msxml-plugin-registrierung/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/msi-1603-msxml-plugin-registrierung/en/</guid>
      <pubDate>Wed, 09 Sep 2026 08:00:00 +0200</pubDate>
      <description>A 3D plugin fails with error 1603 — system-level tracing reveals a missing, long-deprecated Windows component.</description>
    </item>
    <item>
      <title>When the server dies: an emergency migration to new hardware, step by step</title>
      <link>https://solutions.bitblade.io/blog/server-migration-hyperv-notfall/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/server-migration-hyperv-notfall/en/</guid>
      <pubDate>Wed, 09 Sep 2026 08:00:00 +0200</pubDate>
      <description>A total Hyper-V host failure, a day-current backup and two pitfalls: a ghost host and the wrong VLAN.</description>
    </item>
    <item>
      <title>Diagnosis without a mouse: tracing repeated software crashes with PowerShell</title>
      <link>https://solutions.bitblade.io/blog/sidexis-fehlerdiagnose-powershell/en/</link>
      <guid isPermaLink="true">https://solutions.bitblade.io/blog/sidexis-fehlerdiagnose-powershell/en/</guid>
      <pubDate>Wed, 09 Sep 2026 08:00:00 +0200</pubDate>
      <description>A practice client, a repeatedly crashing Sidexis 4 — diagnosed entirely in PowerShell instead of the Event Viewer.</description>
    </item>
  </channel>
</rss>
