Justin C's questions

Looking at my Event Log I see that right now an attempt is being made at brute forcing my 'sa' user for Sql Server on my Windows Server web edition box. I know that firewall rules are not the only solution, but I thought this could be a learning experience. I created a rule to block the offending IP address from inbound traffic for all applications.

The problem is, as I watch, the same IP address continues to log unsuccessful log in attempts. Does anything else have to happen before a rule goes live? Do I need to restart something? Could another setting be over-ruling the new rule? Thanks

I have a Dell PowerEdge 830 server that has been operating as my file server for a few years. I had never had a problem with it, and it been sure to install all BIOS updates.

A few months ago I noticed that the one large CPU fan seemed to be running full power all the time. In the past it would go to full power during boot-up and then only during heavy periods of processing. Now it runs full tilt all the time, no matter what.

The room is well air conditioned. The CPU is barely being used, just keeping Windows running. I can't get any temperature readings though, when I run HWMonitor.exe it is not able to report any information. I couldn't find anywhere in the BIOS menu to adjust the fan speed or temperature settings. Last, I took a can of condensed air to the heat sink and fan to make sure there are clear pathways.

So now I have a dusty room that still has a jet engine in the corner. Any ideas on how I can control this fan?

Also, I should note, the sound is not any different than it used to be when going full power. I don't think there is a problem with the type of noise coming out, just the fact that it never slows down.

EDIT: When booting up the CPU fan does seem to slowly throttle up, then down, then once Windows begins booting it goes to full power and stays there.

Is there a setting in IIS 6 to turn an FTP site off after a specified number of failed login attempts? It has already been documented on this site that a Windows server sitting on a static IP address can record tens of thousands of failed login attempts a month.

One server I maintain has had tens of thousands of attempts made against the FTP port. I have solid passwords in place, so I am not overly concerned. I rarely have to use the FTP, so for the most part I turn it on and off as I need it. Sometimes though I forget to turn it off when I am done, only to find the next day that my EventLog is full of audit failures.

I would want to set a high number, in case I just messed up the password. Something like if 50 failed login attempts happen, just turn off the FTP site. Then if I need it later I can just start it again.