This happens to me as well, and I've been unable to find a fix.&nbsp; The only noable difference b/t your setup and mine is that a segment of the connection b/t my SB and slimserver does run over powerline (though the slim traffic should be the ONLY thing running over that link).

&gt;When playing music on my SB, I experience periodic pauses.&nbsp;&nbsp;They happen, at a guess, every 30 minutes or so.&nbsp;&nbsp;But that's just a guess.&nbsp;&nbsp;When they happen, the SB display freezes (if the song title is scrolling, it stops) and the music also freezes.&nbsp;&nbsp;A short time later (normally 3 or 4 seconds, but sometimes it will last closer to 10) the music and the display resume exactly where they left off.

&gt;

&gt;I play almost exclusively FLAC files.&nbsp;&nbsp;My SB is WIRED not wireless.&nbsp;&nbsp;There is typically very litle network activity on my network, so I don't expect network saturation is causing this.&nbsp;&nbsp;My SB is connected to the server via Microsoft wireless base station/4-port router.

&gt;

&gt;I have server version 5.4.0 running on Windows XP.&nbsp;&nbsp;My firmware level is 40.&nbsp;&nbsp;I have the graphical display.&nbsp;&nbsp;Nothing else runs on the server except the Slimserver software.&nbsp;&nbsp;I recently also installed Norton Antivirus, but I was experiencing this problem prior to the installation.&nbsp;&nbsp;I also recently moved to Windows SP2, but again, I was experiencing this problem prior to that.&nbsp;&nbsp;My system has 512MB RAM and 950MHz AMD Athlon processor.

&gt;

&gt;I have observed this in previous server/firmware levels as well.&nbsp;&nbsp;I don't recall when it first began showing up.

&gt;

&gt;I've also noticed that my music hitches if I am using the web interface to add music to the playlist, although it does not normally pause if I add music using the remote control.&nbsp;&nbsp;I also experience these hitches if I adjust the shuffle setting, whether via remote control or via the web interface.

&gt;

&gt;I saw one Bugzilla defect similar to this, but it wasn't exactly the same, and it hadn't been commented in a while.&nbsp;&nbsp;Is this a known issue, or should I open a defect?&nbsp;&nbsp;Or are there some things I should try first?