Client Security Log on Problem

[ppk800]

Hi All,

Here's my system: T43, Norton Antivirus 2006, Zone Alarm Pro.

After upgrading to Client Security Solution v.7.0 and undergoing some migration processes, I have encountered the following problems:

Though I am able to use my fingerprint to poweron, when windows loads up, I start having a few problems. After windows loads up, a dialog appears and asks me to either enter my windows password or use the fingerprint to log on.

(1) My first problem. I tried to use my fingerprint, but I could not proceed, but instead a dialog box popped up and asked me to enter my windows password. I had to enter my windows password to proceed to my desktop. I do not recall what I did, but after messing with the Client Security Solution software, I am now able to use my fingerprint to log on.

(2) My second problem. After getting past the windows logon step, a dialog pops up and says:

Client Security Log on
There was a problem connecting to a critical service. It is possible that anti-virus or firewall is blocking the connection. Also, check to make sure that the TPM is installed and enabled.

I have checked my antivirus and firewall to make sure, but this problem remains unsolved. Though I can just click OK and proceed, but it's quite annoying to see that message every time I turn on or restart my computer.

Please help.

Mike

[ppk800]

Please help.

[NikeChicago]

After getting past the windows logon step, a dialog pops up and says:

Client Security Log on
There was a problem connecting to a critical service. It is possible that anti-virus or firewall is blocking the connection. Also, check to make sure that the TPM is installed and enabled.

I have checked my antivirus and firewall to make sure, but this problem remains unsolved.

I have a T42 (that I bought from Fry's Electronics) with this exact same problem. Coincidentally I have no fingerprint reader on this machine.

[fcampbel]

No takers? this past weekend, I decided to run Software Installer and just let it install everything it said I needed. Now I have the same problem.

[fcampbel]

Found it, in another thread. Thanks to all who have discussed this:

Forgot to mention one step -- after disabling the security chip in the BIOS, also remove the registry key "cssauth" at: HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Run