Jake Platt writes: I am a network consultant working on Long Island, NY and help support about a dozen small to mid-size companies mainly located in a huge industrial park originally built in the 1950's. In the past 60 days, the Verizon data and voice networks have experienced huge spikes in failures, as many as, 2 — 3 local loop/central office equipment and line failures per week for each of my clients!!! Verizon has been taking 2-3 days to respond, effectively leaving these companies in the dark (no internet, no email, no voice). I've never seen anything like this.
Privately, the Verizon tech support guys have told me that the copper lines in the ground are so old that they are letting the system go into decline and do not want to spend any $$$ to improve it until they have no choice.
Are parts of the US telecommunications network reaching its age limit?
Long Island, NY
thundergeek writes: The company I work for is purchasing thin clients, lots of them! I am responsible for the integration of these thin clients into a redundant failsafe server system consisting of two server 2k3 servers (not my choice) on an Active Directory domain. I want to know from the rest of you admin geeks how I should go about creating some sort of rsync between the two which mirrors, in real time, all the session data created by the clients. What needs to happen in the event of a server failure is a seamless transition to the back up server with minimal data loss and down time. Is there a software solution, or an easy robocopy hack?