O. can't work with NTFS Mounted Volumes :(
Posted in xn--kfs74mzzid01b.com edit by jane on January 9th, 2009
Whats more, I extensively implement NTFS Mounted Volumes - as a convenient w2k's facility.
Furthermore, I have separated ALL installed applications from the OS volume/drive in the way
all applications lie on the SEPARATE drive/volume
which has NO DRIVE LETTER assigned, and which
is MOUNTED to a native folder "D:MyPrograms"
(just near "D:WINNT" and "D:Program Files").
I used the applications installed there for 2 years or so, with NO complain, UNTIL TODAY when I just installed Outpost!
Outpost simply ignores any rules created for the applications on the mounted volume, it apparently MISSIDENTIFIES them!
Those applications simply are not allowed to connect to the Net - whatever the rules!
The only remedy is to check the global "policy" option as "Allow Most", but as we know it disables FW :(
Also when the questioned application's rules are removed from the "Application" tab settings, and the "policy" is set to "Rules Wizard" then after answering "Allow all activities for this application" on popup question - the application IS allowed indeed BUT just ONCE (as if "Allow Once" had been chosen instead).
Why can not Outpost properly bind rules to programs installed on NTFS Mounted Volumes? What to do?
2) try to use letters, just for test
I tried it methodically for several applications which I found to change easily access path (form the OS point of view).
THEY WORKED WITH THE RULES PERFECTLY this time!
So, do You advice to re-plant the WHOLE BUNCH of nearly 30 applications to make them accessible by drive letter NOW?!
Could You give a clue how to re-configure the System, registry etc. to reflect all those paths changes?
Originally posted by Adrian
Outpost simply ignores any rules created for the applications on the mounted volume, it apparently MISSIDENTIFIES them!
Those applications simply are not allowed to connect to the Net - whatever the rules!
Perhaps this is because Outpost identifies applications by path, filename, and MD5 signature. Maybe Outpost is having a problem with the path, in which case it will not recognize the application. This may be due to the way you setup your system. Honestly, I am not sure and this is just a guess.
Originally posted by Adrian
Why can not Outpost properly bind rules to programs installed on NTFS Mounted Volumes? What to do?
As I said, I am unsure. I recommend contacting Agnitum directly through this link:
Agnitum Online Support Form (http://www.agnitum.com/support/supportform.html)
I will refer this thread to a friend of mine. Perhaps he has an answer. If not, I believe that you may have to use the support link that I have given.
Have a good day. :)
Unfortunately, OP has a problems with NTFS mounted volumes, mostly beause of (unconfirmed)bug in using a file path in the low-level kernel driver, which OP is installing. and this bug probably affect both of finding OP configuration file and operation with application path to find a suitable rule in the configuration file.
I can picture a several solutions of this problem:
1) install OP to default folder "%systemdrive%:Program Files"
2) try to use letters, just for test
3) wait for a new version, where, we hope, this issue is amended.
#If you have any other info about this subject , Please add it free.# |
