Wow, there are some IT-companies out there botching together systems and networks... :?
Today I received a call from one of our customers that an acquaintance of him working in another company which we don't service has a problem with one of their mail accounts. They changed the password at the mail provider but since then that mail account doesn't receive mails anymore. Our customer tried his best yesterday to solve the problem, but failed to do so.
I contacted the acquaintance of him to solve the problem, they let me on the machine for a remote support session.
The machine is a Windows Small Business Server 2011 (based on Server 2008 R2, bundled with Exchange 2010 and some other crap) which I know since we have some installations at our customers, too. The thing is that the physical server (not virtualized) has just
4 GB of RAM. :shock: I thought 8 GB in a server of a customer of us who we adopted was low, but an SBS 2011 with 4 GB is
painfully slow.
Anyway, I fixed the problem (they fetch the mail via POP3 so the password for the mail account had to be changed there, too), but they had another problem: Our customer really made a mess, he disconnected the old mailbox with all the mails from the user and set up a new mailbox in the hope of getting the new mails to work. Additionally, he tried setting up a new Active Directory user which didn't work either. So I had to disconnect one mailbox from the user and connect the old one with the old mails (thankfully the mailboxes aren't deleted right away...). Carve something into stone is quicker than those tasks...
Next thing: the client-PCs (thankfully Windows 7, but with Office 2003) aren't domain-joined so the password for the mail account in Outlook had to be set manually, and every time the user changes his password in Active Directory.
But the problems didn't stop there: their smartphones didn't synchronize with their Exchange Server anymore. They told me the settings of the smartphones, and they have a DynDNS address as server address. One problem was that they just replaced their defective router with a new one which of course didn't have the login data for that DynDNS account. The next problem was that the DynDNS account used before is from a IT company which doesn't work for them anymore (I'm not surprised why...) so they had to set up a new DynDNS account with a new DynDNS address. The third problem was that the router is a measly Fritzbox which can only forward ports, but doesn't scan anything when ports are forwarded. I hesitantly set up the port forwarding, not without warning that their Exchange Server Outlook Web Access is now reachable from the internet without protection.
Oh, and of course when they set up the new Fritzbox they didn't disable the DHCP-service so the DHCP-service of the SBS stopped itself when it detected the other DHCP-server in the network. They were lucky that the server had an IP ending with .110 and the Fritzbox allocated IP adresses from 20 on...
While I was at it I discovered that their internet connection has 850 kbit/s down- and 160 kbit/s upload.
Those tasks which would have been about 45 minutes on a normal system (including explanations to the customers what DynDNS is for, what a DHCP-server does and whatnot) lasted 3 hours...