@kalagesan and @apaul
What I've done:
-reset IC services
-set Juniper EAP-TTLS as an auth method in windows 802.1x supplicant
-set "anonymous" in properties of this EAP-TTLS method in the field "Anonymous"
-verified that on the IC in Users-->Junos Pulse-->Connections-->Default i have only one connection called dot1X of type (UAC 802.1x)
-verified that in dot1X I have Outer username set to anonymous and that I trust Client side CA server
After those changes I get the same messages as I did previously - auth unsucessful contact administrator. The logs from Junos Pulse Client are useless because the client waits for the 802.1x auth and only then connects to the IC via IP.
I wonder about one more thing. My connection dot1X is of type UAC 802.1x but I don't see it on the PC in Junos Pulse Client. What I see there is a connection to the IC IP address (L3). Is this correct?
Hi,
Now I got the problem, You should see a dot1x profile named Local Are connection in pulse UI for dot1x. This is the dot1x profile pushed from the IC when you download the puls e client from IC or installing the preconfigured pulse msi file downloaded from IC.
Can you dowload the pulse client for dot1x directly from IC server using agentless access if possible to the PC else can you try downloading the preconfigured pulse msi file from junos pulse connections from IC.
installingthis preconfigured msi file from junos pulse will solve the issue
I hope this should help
Regards,
Kannan
YES!!! That was it Auth was successful, network is working.
I've used a preconfigured settings file with downloaded Junos Pulse Client msi installer.
Example command: msiexec -i JunosPulse.msi CONFIGFILE=c:\temp\myconfiguration.jnprpreconfig
After that I have my Local connection in Pulse UI. When connecting I'm prompted for username and password. And finally only one license is eaten up on the IC
It makes me curious, though. Previously I've deploed Junos Pulse Client by allowing full access to the network for the PC and then opened up the IC in the browser. The realm has agent option (Pulse) enabled on it. After successful installation there was no 802.1x connection in the UI.
Maybe automatic preconfig installation is available only with the agentless option You've suggested and with manual installation? I will try the agentless option later.
Thank You for Your help. Sometimes the answer is so close that we don't see it
Hi,
I am glad that my suggestion helped you in issue resolution, happy to help you in future
Regards,
Kannan