May 17, 2016 9:45pm
I've been troubleshooting a connectivity problem that so far Pulse TAC hasn't been able to figure out. We're evaluating Pulse Secure for a possible deployment, so I'm hoping someone might have an idea.
Here's what's happening: My Windows 10 laptop is our standard corporate build. The default login is our corporate domain and username, and the laptop connects and authenticates fine on the corporate network. When the laptop is connected to a cable modem and thus the Internet, we have it set up to also log in with the same domain credentials, and to launch the PCS client before the login is complete, in always-on mode. Here's the problem: The client is sending the username to the concentrator as domainusername, and our DC is rejecting that as an invalid user account. But, if we cancel and then try to reconnect manually with the client using just the username, it connects just fine. I've run lots of policy trace logs on the appliance and the issue is the username. I'm wondering if there's some way to strip the domain from the username using a filter on the appliance, or to change it on the client side.
Client version: 5.2.2 (343)
Appliance: 8.2R2 (build 44173)