New potential client asks me to look at their network. They're using Terminal Server on a Server 2000 box. Remote office is seeing pings of 200 - 10000ms (!) to the server.
Everything checks out at the remote office so I went to see the main office where the server is located.
All they're using the server for is file serving and Terminal Services.
Ready for this?
Server is on a static IP cable connection - it is NOT behind a router or a firewall. No software firewall running. No critical updates ever installed. No IIS lockdown (mail, web and ftp servers are running and FTP can be logged into via anonymous login).
Server's wide open only being thinly defended by VERY unsecure passwords (less than 4 digits - all letters!).
The reason they're seeing such high pings to the office with the server is because the server is hogging all the bandwidth doing God only knows what: spam relay, DoS relay, warez FTP server (take your pick or choose all of the above). If I pull the plug on the server, the Internet connection is good and fast. Plug it back in and the pipe is maxed out.
Here's the good one: The previous IT consultant says the latency problem is due to the cable modem at the main office and they should have Road-Runner replace it.

I don't usually have to deal with someone else's screwups that are this bad - and I 've NEVER seen such an exposed and compromised server. Shit ANYONE has the common sense to at least put the server behind a router and use port forwarding!
Anyone want to chime in with a list of what trojans I'm likely to find? Norton Anti-Virus Enterprise is running and up-to-date, but that doesn't mean shit. It may be compromised, and I know there's some Spam relay trojans out there that are just modified Spyware and Norton won't detect them as viruses.
Needless to say I'm going to lock down IIS right off and probably slap a firewall on it as an immediate short-term solution (yeah, just a bandaid, but can't distrupt the office too much during business hours). Then do all the critical updates.
Eventually I have to get the bitch behind a router or (preferably) a VPN router.
Heck, I may even have to get the static IP changed depending on who's been hacking the box. For all I know someone's using it as a porn server.
Sigh.... I have to decide if I even want to take this one on - it's a long drive and it's going to be a LOT of work. Not sure I can spare all that time that far off the beaten track. I feel sorry for them though. Nice people and referred to me by a very good client



