So it was a relatively painless upgrade and reconfiguration of our site network. Think we got it right. Past few days we have had a few periods of up and down with our site and broadcast.
Combined all of our broadcast, database and web services into 1 speedy intel dual 2.4ghz server. Upgraded our DSL modem to a DLINK ADSL2+ modem. Now our entire network uses DLINK high performence routers, bridges and access points.
Already seeing better performence with our internet dataline. If we have any issues with Highlander Radio buffering, we will put in place some bandwidth throttling, but otherwise this was the fastest and cleanest upgrade/reconfiguration we have done.
Next on our plate is converting our old radio server into a Microsoft Home Server 2003 which will automatically backup all of our data every night thereby insuring that Celtic Radio lives on in the event of a major hardware failure!
New router is in place - expect better connectivity going forward. Today we had alot of drops and had to keep reseting our router to keep up with traffic. Should be better service starting now. We may need to reset the router a few times tonight for configuration data.
Is it due to lightning and power surges, or just general wear? The nation seems to continue to be under a lot of rain and storms.
Interesting question. We have been wondering ourselves. The router we had in place - the DLink 4300 actually was our longest running router for about 1.5 - 2.0 years.
We suspect that perhaps our new DSL modem, Dlink DSL2320B 2/2+, boosted our network performance by 35% and maybe heated up our old router and caused a hardware failure. Basically the router was stuck in a network test mode!
Here is a spec sheet on the new router. It has a little top side display panel which gives us intant status on the network. Hopefully we will get atleast 2 years out of this one!
At 9:30 EDT when I try a request I get request failed for the following reason Unable to connect to 220.127.116.11:1221. Highlander Radio might be offline. The error returned was Connection timed out (110).