T500 Fingerprint reader does not work reliably
Posted: Fri Dec 11, 2009 1:04 pm
I have T500 with Windows 7. I want to use other firewall than Windows Firewall. I have a life time license to Outpost Pro firewall. It appears that there is a problem: it has a compatibility issue with fingerprint reader software (cssauth.exe and FPapp.exe).
But if I want to modify my fingerprint settings, it fails. I can see that FPapp.exe tries to connect local TCP port 5550 but can not reach it. Same is true with cssauth.exe and sometimes with logonui.exe (fingerprint login is then not available. This is not always. Mostly fingerprint login works ok).
If I uninstall Outpost, everything works ok.
If I run hardware test to fingerprint reader, It claims that reader is working ok!
Does anybody know what is this TCP port 5550? How can I allow FPapp.exe and others to have access to it? I am afraid that at boot time or login time some service is trying to open port 5550 for listening (so that other software may access fingerprint reader services), but Outpost denies that request or interferes that process. Then when FPapp.exe and others try to connect to that port, it is not available.
I did contact Agnitum support. They are trying to find solution.
But I also wanted to ask this forum, because someone of you may know this already.
Any ideas?
But if I want to modify my fingerprint settings, it fails. I can see that FPapp.exe tries to connect local TCP port 5550 but can not reach it. Same is true with cssauth.exe and sometimes with logonui.exe (fingerprint login is then not available. This is not always. Mostly fingerprint login works ok).
If I uninstall Outpost, everything works ok.
If I run hardware test to fingerprint reader, It claims that reader is working ok!
Does anybody know what is this TCP port 5550? How can I allow FPapp.exe and others to have access to it? I am afraid that at boot time or login time some service is trying to open port 5550 for listening (so that other software may access fingerprint reader services), but Outpost denies that request or interferes that process. Then when FPapp.exe and others try to connect to that port, it is not available.
I did contact Agnitum support. They are trying to find solution.
But I also wanted to ask this forum, because someone of you may know this already.
Any ideas?