I have a real puzzler here. For one user we get "The View Connection Server authentication failed" when trying to sign in with the View 4.5 client via the public URL of the Security Server. Here's what DOES work: I can sign in as anyone else on his Win 7 domain-member laptop and connect to that alternate person's VM no problem. I can sign into the laptop as him and authenticate to View as anyone but him no problem. I can sign in as him from any other LAN or Internet-connected PC and authenticate to View as him no problem. I can sign in as him from his laptop while on the LAN and connect to either connection server directly as him.
The two things that DON'T work are: I cannot sign in to his laptop as him and authenticate to View as him, and I cannot sign in to his laptop as anyone else and authenticate to View as him.
Our setup: Security Server 4.5.0.3082 in the DMZ; two Connection Servers (4.5) on the same internal subnet with a firewall hole through to the one dedicated to the Security Server; View Client 4.5 on Windows 7 Pro 32-bit.
His password is not locked out, and no Failure Audit messages appear in any of the servers' Security event viewer logs. I have deleted his user profile and changed his password. I have signed in as Domain Admin on his laptop and run the View Client "administratively". I have disjoined and rejoined his laptop to the domain.
My initial thought is that the Security Server is caching some bad credentials that only apply to him on this particular machine, but that is a complete guess. Any ideas?
-Andrew
Message was edited by: ACaplinger to add Tags