492 reputation
1930
bio website youtube.com/…
location The swinging 60's!!! YEAH BABY, YEAH!!!
age 29
visits member for 1 year, 11 months
seen Jan 23 at 20:36

Scott Evil: I hate you! I hate you! I wish I was never artificially created in a lab!

Dr. Evil: Scott, that hurts daddy when you say that. Honestly.


Jan
19
awarded  Popular Question
Jan
18
awarded  Notable Question
Jan
13
awarded  Popular Question
Jan
13
awarded  Popular Question
Jan
5
revised Troubleshooting unusual server room power issue. (Suspected power surges or spikes)
added 2 characters in body
Dec
30
comment Troubleshooting unusual server room power issue. (Suspected power surges or spikes)
@derobert that's one of the things we're looking at trying now. There must be something happening that we can detect, even when it's not causing things to malfunction. We checked the UPS logs and it wasn't seeing any surges or spikes. This is strange because whatever happened went straight through the UPS and hit the servers the other side of it, so you'd expect it to have a record of something.
Dec
29
revised Troubleshooting unusual server room power issue. (Suspected power surges or spikes)
added 12 characters in body
Dec
29
comment Troubleshooting unusual server room power issue. (Suspected power surges or spikes)
@ekaj sure. We had a day of around 50% downtime due to this last week but since then everything has worked perfectly. I'll wait a while and report back with any new info or clues I find in the UPS logs.
Dec
29
revised Troubleshooting unusual server room power issue. (Suspected power surges or spikes)
added 2 characters in body
Dec
29
comment Troubleshooting unusual server room power issue. (Suspected power surges or spikes)
@joeqwerty I'm contacting the access control system company to see if the system logs power events and to see if they've ever seen a power issue hard reboot the system before. I'll check the UPS logs. ekaj - we've only just moved into this building and the first day the users came into the office everything in the server room started rebooting without warning. This could have been because the air conditioning was not turned on until the same day but also there was more load on the PoE switches. Hard to say now as the problem has stopped happening and the HVAC is still running.
Dec
29
revised Troubleshooting unusual server room power issue. (Suspected power surges or spikes)
added 103 characters in body
Dec
29
asked Troubleshooting unusual server room power issue. (Suspected power surges or spikes)
Dec
24
awarded  Notable Question
Dec
15
awarded  Notable Question
Nov
26
awarded  Caucus
Nov
24
awarded  Excavator
Nov
24
revised OK, so I'm running a Windows Server 2008 and my friend called me an idiot for not using remote desktop to administrate it. Why?
Fixed spelling and punctuation
Nov
24
suggested approved edit on OK, so I'm running a Windows Server 2008 and my friend called me an idiot for not using remote desktop to administrate it. Why?
Nov
24
comment Does windows Remote Desktop have any protection against brute force attacks?
Don't take it personally! :) It takes under an hour for an attacker to find internet-facing forwarded RDP ports and to start brute forcing them dozens of times per minute. Anyone who follows that advice will get locked out all the time. Instead, you could create a rule in Windows Firewall to only allow inbound connections from "good" IP ranges (i.e. your own). Using a 3rd party tool like RdpGuard to automatically block bad IP addresses, or using SSH (as suggested by Ryan Ries). Those are three better solutions which won't get you locked out of your own server right there! :D
Nov
24
comment Does windows Remote Desktop have any protection against brute force attacks?
This should not have been marked as the answer. It's a lazy man's solution which just causes another problem - your domain administrator account will get locked out. A useful solution would involve blocking connections from a consistently failing source IP address, not locking out the user account which is the target. You're basically just making it possible for the attacker to do a DOS attack on you by locking you out whenever they want. Sure, use this as a last line of defence but not your first line of defence. That should involve blacklisting the attacker's IP address.