I am having the same problem as the rest of the post chain, regular appearances of "Server Connection Interrupted".
My occurrence is slightly different. I have three Time Capsules, on my network, they are all wireless off, connected to a Cisco switch via Ethernet. There is an Airport Extreme Base Station and two Airport Express. All TCs and the AEBS and AEs were purchased within the last 6 months of 2011.
Previous to the "Server Connection Interrupted" messages appearing I used a Cisco RVS4000 to manage DHCP, and firewall etc on the network. The AE was used as a WAP. In this config, I never saw the "Server Connection Interrupted".
After upgrading my DSL account to get higher bandwidth I removed the Cisco device and reconfigured the Airport Extreme to be a full feature WAP, router etc. The firmware on all Tcs and the AE was 7.5.2, in this config the "Server Connection Interrupted" didn't appear. I upgraded the TCs and AE to the latest firmware, 7.6, and the warning boxes started appearing regularly.
The "Server Connection Interrupted" warning only seems to appear on TCs that are not being accessed or have not been accessed for a period of time, I am not sure how long that period is. I would look at the WAPA Group Key Timeout on the Wireless Network Options tab of the AE first, the default is 1 hour. It would be interesting to note whether the appearance of the dialogue "Server Connection Interrupted" dialogue is around the time the Group Key changes?
Perhaps the DHCP server in the AE is treating a drive as disconnected because it is not responding properly when the AE polls it after the key has changed.
It could also be that the 7.6 firmware on the AEBS is not managing the polling of attached but inactive devices properly. I have downgraded the firmware to 7.5.2 on one of the TCs that regularly report the "Server Connection Interrupted" error and the AEBS. So far, the two TCs running firmware 7.6 are reporting disconnected periodically, the TC that was downgraded to 7.5.2 has not!
As I changed the firmware on a TC and the AEBS at the same time it is not possible to pin the problem to the AEBS firmware or the TC, but I am going on the assumption that it is the TC and am downgrading all three TCs to 7.5.2.
M