Don't know if this post fits here or not but it was the closet match.........

Here's the run down so far:

I have about 47 workstations done with no problems, but one is giving me the following error on login.
>> ---------------------------
>> Windows Security Message
>> ---------------------------
>> Unable to log into the network because the login credentials or the server
>> certificate is incorrect.
>> ---------------------------
>> OK
>> ---------------------------

All other users are authenticating w/o problem. After reviewing/researching, we checked to make sure the user in question did have 2 concurrent log ins suggested by a post in the forums. We also removed the ZCM agent and reinstalled on the workstation. Same result (message above). User would receive the exact same error at another workstation but other users could log in w/o a problem on said workstation.

In the documentation troubleshooting section (I think), we found the following:

>> Large number of concurrent client logins might result in login failures
>> Explanation: The maximum number of concurrent client connections that a
>> server can
>> support depends on the configured Connector acceptCount. If the
>> number of concurrent client requests exceeds the value of Connector
>> acceptCount,the client connect requests might fail because the server is not
>> able to accept these connections.
>> Action: Increase the number of client connect requests that the server can
>> support.

>> On a Linux server:
>> 1 Log in as root.
>> 2 Open the /srv/www/casaats/conf/server.xml file.
>> 114 ZENworks 10 Configuration Management System Administration Reference
>> novdocx (en) 11 July 2008
>> 3 In the Define a SSL Coyote HTTP/1.1 Connector on
>> port 2645 section, change the value of the Connector
>> acceptCount to the desired value. A value of 300 is optimal.
>> 4 Restart the Authentication Token Service:
>> 4a At the server prompt, go to /etc/init.d/.
>> 4b Run the casa_atsd restart command.

We did this and it seems to have fixed the problem. However, the $100,000 question is with only about 50 workstations deployed so far, why would the server reach it's maximum number of connections?? It sounds to me like the clients are not releasing their connections on log off and then just using another connection on subsequent log ins. So, has anyone else out there seen this behavior and if so, how do we fix it? Is there a way to check how many connections are in use? Is there a way to disconnect "unused" connections? Any troubleshooting help?