Posts Tagged ‘windows server’

Checksum a directory with md5deep

February 28th, 2010

md5deep checksums

File integrity is no joke and system administrator know this is a problem that can result in unnecessary support tickets. If the users can be provided with the hash of a working document it can help narrow down the amount of variables. The problem administrators face is that unlike users, administrator have to manage servers with hundreds of thousands of files in each directory that have to be hashed. This lends it self to a few problems : hashing file by file is out of the question and a waste of time, which means we are left to find a solution that can work on a recursive manner.

Recursive operation – md5deep is able to recursive examine an entire directory tree. That is, compute the MD5 for every file in a directory and for every file in every subdirectory.

On the Windows platform you can use md5deep which is cross platform, works perfectly on Windows and best of all can handle a large number of files without breaking a sweat. It will literally create a checksum for all the files on the directory where md5deep is being used, the results are then exported to a single file where they can be used for verification at a later time.

md5deep is a software package used in the computer security, system administration and computer forensics communities for purposes of running large numbers of files through any of several different cryptographic digests.
Source: Wikipedia http://en.wikipedia.org/wiki/Md5deep

md5deep is managed from the command line, however it’s very easy to use considering it will be in charge of creating checksums for a large number of individual files.

How do we use it ?

md5deep example

First of all you can download md5deep from SourceForge.net.

After you download md5deep I recommend you move the executable to the C:\Windows directory for easy access from the command prompt.

For this tutorial I will be hashing a single directory. Start by opening the command prompt :

Start > Accessories > Command Prompt

On the Command Prompt type :

md5deep -rel "test_directory" > results_file.md5

Explanation of the command

  • r = recursive operation
  • e = compute estimated time remaining for file name
  • l = print relative paths for file name
  • “test_directory” = this points md5deep to the directory you wish to checksum
  • > results_file.md5 = is the file where all the results will be written to, you can name it whatever you want.

After md5deep is done you can open results_file.md5 to view and analyze the results.

Conclusion

md5deep is a simple tool that should be part of your arsenal, it might come in handy at a later time. Keep in mind that md5deep like tools will always require processing power, so try to use it during the light hours of the day.

md5deep Home page
Md5deep manual

Enable ping on Windows Server 2008

February 12th, 2010
I am unable to Ping my Windows Server 2008 box, how can I enable Ping?

By default Microsoft disables Ping on the Windows platform, probably has an added security measure. However Ping maybe needed for testing or monitoring purposes. The process to allow Windows Server to respond to Pings is minimal, requiring minimal changes to the Windows firewall.

Go to Start > Administrative Tools > Windows Firewall with Added Security

start-control-panel

On the sidebar look for Inbound Rules > File and Print Sharing (Echo Request – ICMPv4-IN) > right click on Enable Rule

enable-rule

The rule has now been enabled and the server will respond to Pings.

rules-enabled

If you wish to later disable ping all you have to do is right click on the rule and select > Disable Rule

Wireless adapter for Windows Server 2003 and 2008

November 30th, 2009

There are plenty of wireless adapter(USB/PCI) that work on Windows XP and Vista without a problem(most of the time). But I have yet to find one that officially supports Windows Server 2003 or 2008. It’s not uncommon to use one only to end up with repeated BSOD’s. I don’t think the administrator is going to be happy with ‘just reboot the server’.

Yes, this assumes you have no way of using wires.

An unstable driver is not something that should be impacting server performance. Since I’ve given up all hope of ever finding supported drivers I had to come up with an alternative solution.

The solution

Meet the Linksys WRT54GL and the open source firmware Tomato. The same combination that delivers a stable router can also be used to act as a wireless client.

Wireless Client

You are not limited to the WRT54GL, you can use any device that supports the wireless client feature

The wireless device will no longer act as a router but as an adapter for any devices that need wireless connectivity by receiving the signal and allowing wired devices to connect to the AP, think of it as a bridge.

Tomato Wireless Client

Disable The Shutdown Event Tracker on Windows Server

November 20th, 2008

Networking is a complex process that requires annoying ways of keeping track of what’s going on. One of the ways to keep track of why a server was shutdown or rebooted in windows 2003 / 2008 is by means of requiring the user to provide a reason for the action before executing the request.

The Shutdown Event Tracker is useful if you run a big network with multiple server or have little control over day to day activities on the server. The opposite happens on a smaller network where usually one person is in charge and the only one responsible for maintenance. In my case I have a test server at home.

To disable the Shutdown Event Tracker go to Start > Run, and type gpedit.msc

On the right pane double click on Computer Configuration > Administrative Templates

Double click on System

Scroll down and search for Display Shutdown Event Tracker and double click on it

Select Disabled, then just click OK

From now on whenever you attempt to shutdown the server no event tracker windows will appear asking you for a reason.