As discussed above in the comments you first need to enable the interpretation of those .htaccess style files. Before you do that they are simply ignored.
For that apache offers the command AllowOverride. Place it inside the <Directory ...> section of your host configuration which defines the rules you want to have applied to the location where you want those files to be interpreted. So something like:
Listen 80
<VirtualHost *:80>
ServerName www.example.org
DocumentRoot "/var/www/documents"
<Directory "/var/www/documents">
AllowOverride All
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
Your .htaccess style file need that content:
Order deny,allow
Deny from all
That should work, as far as I can say without trying it now myself.
Anyhow you really should start monitoring your http servers error log file (also as already written above in the comments). It allows you to understand what is wrong with your setup, for example in case of syntax errors. The typical location of that log file is something like /var/log/apache2/error.log, but it might vary, depending on your setup again. Look for the CustomLog command in your apache configuration which defines the location of that log file.
I would like to repeat my second comment here however:
You want to think about if you really need to use .htaccess style files. Why don't you place your commands in the host configuration instead? .htaccess style files are notoriously error prone and unreliable, they are hard to debug and really slow the server down. They are only offered for those users who do not have control over the host configuration (as it often is the case with cheap web space providers).
You can achieve the same result without any .htaccess style file by adding another <Directory ...> command to your host definition:
Listen 80
<VirtualHost *:80>
ServerName www.example.org
DocumentRoot "/var/www/documents"
<Directory "/var/www/documents">
AllowOverride All
Order allow,deny
Allow from all
</Directory>
<Directory "/var/www/documents/protected/area">
AllowOverride All
Order deny,allow
Deny from all
</Directory>
</VirtualHost>
.htaccessstyle files. Take a look at apachesAllowOverridecommand. - arkascha.htaccessstyle files. Why don't you place your commands in the host configuration instead?.htaccessstyle files are notoriously error prone and unreliable, they are hard to debug and really slow the server down. They are only offered for those users who do not have control over the host configuration (as it often is the case with cheap web space providers). - arkascha