- Pulse Secure Community
- :
- About rrosiak_
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
10-29-2017
10-29-2017
rrosiak_
Occasional Contributor
11
Posts
0
Kudos
0
Solutions
03-13-2013
09:35:AM
I had simillar problem with OAC on Windows XP SP3 on few PCs. The ethernet adapter was missing in the OAC and I was not able to solve it in any way. Even the full OAC reinstallation did not solved issue. I had to use the "pulse-cleaner" that was provided by JTAC to solve this issue. Then I installed once again OAC and the ethernet adapter appeared on the OAC list. I think the "pulse-cleaner" application should be available on the Juniper download portal together with OAC.
... View more
09-10-2012
03:16:AM
In the Network Access -> "Radius Return Attribute Policies" you can specify the Interface which endpoints on the configured VLANs will use to connect to the Infranet Controller once they will be assigned to a role. You are using probably the default setting which is "Automatic (use configured VLANs)". You can change it to "Internal" or "External" IC interface.
... View more
07-19-2012
12:48:PM
Hi, SRX is an L3 auth enforcer. L3 auth means that MAG pushes an auth entry based on role-mapped resource on SRX. SRX is using an IP of the end-user station to create a proper IP-source UAC rule. When first user will authenticate, then all other users will share the same resource access, because SRX is simply not able to distinguish those users. For the SRX that particular IP address (Citrix server) is already authenticated.
... View more
04-27-2012
08:25:AM
Hi, I'm evaluating the OAC 5.40.19175.0 on WinXPSP3 and Win7SP1 x64 with 802.1x machine and user configuration with EX2200 edge swiches. Everything is working properly when I'm working for some time already on the Windows - a full 802.1x authentication and host checks takes around 20 to 50 seconds. However strange things happens when I'm booting the Windows, because it takes about 4 to 5 minutes for the first time when OAC + hostchecker have to start all services. The 802.1x authentication on the switch timeouts (I can set max. 60 secs supplicant-timeout on EX) so the OAC have to repeat for the 2nd time the whole 802.1x auth + hostchecking. I have checked it on WinXPSP3 and Win7SP1 x64 with the same result - OAC startups very slowly on Windows bootup. I've tried already to disable all other 3rd party Windows services, however OAC is still very slow during Windows bootup. I see only jnTccService.exe process that takes from 0 to 2 % CPU usage. In a normal OAC auth situation jnTccService.exe process takes 100% CPU usage. What's happening with Hostchecker on Windows bootup ? Is it a normal behaviour ?
... View more
04-13-2012
05:22:AM
Hi, The problem is that I can't remove the " client authentication " feature for 3rd party certificate, becase 3rd party application needs it. I think the solution could be a feature in OAC where you can enter the certificate attribute name and the expected attribute value, so that OAC could filter out all certificates with "client authentication" to select one, proper OAC machine certificate. Unfortunately as I understand there are no such feature.
... View more
04-13-2012
05:02:AM
Hi, I must say I totally agree with rswinter. We were waiting for the official AD2008R2 support in UAC too long. I believe that majority of Junipers UAC installations are based on Windows domain environment so support for the latest Windows AD version is especially important. The retail availability of Windows Server 2008 R2 was October 2009. Juniper released the UAC 4.2R1 version on march 2012, so we had to wait 1.5 years. So it really took too long to solve this issue. We should wait no more than few months. Some features on NAC are critical, and I think the support for the latest Windows Server version should be amongst them.
... View more
04-12-2012
08:04:AM
Hi, There is one certificate for OAC machine authentication with Intended Purpose with "client authentication". Other certificates were generated by 3rd party application and the Intented Purpose is set to "ALL", so that includes "client authentication" as well. I've tried to revoke and regenerate the OAC machine certificate several times and the "Automatic certificate selection" feature selects sometimes a proper OAC machine auth certificate and sometimes the wrong 3rd party certificate. I do not really understand what is the algorithm here for choosing the certificate. We can't delete 3rd party certificate or change the Intented purposes there. Is there any workaround to select a proper OAC machine certificate when there are multiple "client authentication" certificates in local computer personal store ?
... View more
04-11-2012
08:13:AM
Hi, I have computers where there are several certificates in the computer personal store. One of them is a certificate for OAC machine authentication signed by special CA. When I will choose manually this certificate I can succesfully authenticate this machine. I need however to select the "Use automatic certificate selection", because I'm preparing remote installation for many computers. Unfortuntely OAC 5.40.19091 selects the wrong certificate that is on the computer certificate personal store which is not the certificate for 802.1x machine authentication, so the verification of that certificate fails on IC and the whole 802.1x authentication fails. Is there any way to tell OAC, to select any certificate that was signed by selected CA ? It seems like OAC now doesn't care which certificates it chooses when "Use automatic certificate selection" option is selected.
... View more
04-10-2012
02:00:AM
1. Yes, I've tried to reinstall the driver several times including rebooting PC each time when I uninstalled the OAC and then again when I reinstalled it. 2. I have just tried to install the latest Intel 82567LM driver from Intel web-site (17.0.200.2 version), however I still do not see a driver. I see only the errors every 2-3 seconds that I posted earlier. 3. I've tried to install the same OAC 5.40 on another machine with the same Windows XP version and I did not experience this issue. However there were no previous OAC version installed and the hardware configuration is different. Also its strange that the earlier version of the OAC was working properly on the machine on which OAC 5.40 is now not working. So it seems for me like something is wrong with Windows registry or OAC driver/configuration. 4. Yes, of course. 5. I'm trying to connect to wired Intel 82567LM NIC. The PC is HP Compaq 6000 Pro SFF PC - Windows XP Professional with SP3, 2 GB of RAM, Pentium Dual-Core CPU. Is there any way to clean the whole OAC installation including Windows registry and all OAC folders/drivers ?
... View more
04-05-2012
07:51:AM
Hi, I'm evaluating the new UAC 4.2r1 software and the new OAC 5.40.19091 supplicant. Unfortunately when I upgraded the OAC on some desktop PC (WIndows XP SP3 connected to the AD domain) the OAC do not see any network card under the Adapters tab anymore. I see the following errors in the log every few seconds: --- CUT --- 16:16:29.068 1 odClientService.exe OdysseyKernelIO2.cpp:264 JNPRNA Startup 16:16:29.068 1 odClientService.exe OdysseyKernelIO2.cpp:264 JNPRNAAPI.DLL Version: 5.30.1.17899 Feb 7 2012 14:45:49 16:16:29.068 1 odClientService.exe OdysseyKernelIO2.cpp:264 CreateFile() Windows Error =0 16:16:29.506 1 odClientService.exe OdysseyKernelIO2.cpp:264 Cannot connect to JNPRNA.SYS. Is driver loaded? Error=IPC Failure(e0000101) 16:16:29.506 1 odClientService.exe OdysseyKernelIO2.cpp:264 JNPRNA Shutdown --- CUT --- I've tried to reinstall few times the OAC and to clear manualy the directories and registry entries as you have described it in the article http://kb.pulsesecure.net/InfoCenter/index?page=content&id=KB10554 , however I still see this error. Also there are no errors when I'm installing OAC. How I can solve this issue ?
... View more
03-02-2012
11:44:AM
Hi, can you please update us when the IC 4.2 will be officially available ? Do you supports IC 4.2 Beta2 in production environment ?
... View more
Latest Tags
No tags yet
© 2017 Pulse Secure, LLC. Use of this website assumes acceptance of our Legal Notices and Privacy Policy.
Pulse Secure has updated its Privacy Policy effective June 28, 2017.
