Failed To Authenticate With Ive. Error 104
Contents |
via machine credentials failure on Windows 8 and 10, but works with Windows 7 KB22739 - [SBR] Unable to ncapp> failed to connect/authenticate with ive. error 2 assign the profile to a LDAP user KB40155 - Role-mapping and
Ncapp.error Failed To Authenticate With Ive
resource policy rules are missing after upgrade to 8.2R1 KB23640 - Unable to connect to a Windows
Juniper Pulse Linux
Terminal services resource via the bookmark page KB17848 - Access issues and timeout errors when PCS devices are in a Load Balancing configuration KB15998 - Unable to load
Juniper Network Connect Linux
the custom page zip file due to directory limit KB16896 - Authenticating and creating Role mapping Rule based on a certificate attribute at the realm level for end users in PCS KB17484 - [SBR]Unable to authenticate through SBR Enterprise when enabling PrequalifyChecklist and configuring appropriate check list attributes for the Windows domain users What would you juniper vpn ubuntu like to know? Reset Search Search < Back to search results KB40158 - Unable to authenticate due to a white space in the realm namePrintable View «Go BackInformation Last Modified Date9/13/2016 11:19 PMSynopsis Problem or GoalWhen an end user attempts to authenticate with Pulse Secure Linux client using a realm name with a white space, the following error messages will appear in the ncsvc.log. 20160214214035.222923 ncsvc[p3912.t3912] dsclient.info <-- 302 https://XXX.XX.XX X.XXX/dana-na/auth/url_default/welcome.cgi?p=failed (authenticate.cpp:213) 20160214214035.223024 ncsvc[p3912.t3912] dsclient.error state login failed, error 104 (dsclient.cpp:353) 20160214214035.223374 ncsvc[p3912.t3912] ncapp.error Failed to authenticate with IVE. Error 104 (ncsvc.cpp:253) CauseThis is due to an issue with the PulseSecure.sh script. SolutionThis issue will be resolved in 8.1R8 and 8.2R2. To workaround this issue, use pulsesvc instead of PulseSecure.shFor example: /usr/local/pulse/pulsesvc -h test.acmegizmo.com -u user1 -p PulseSecure -U https://test.acmegizmo.com -r "Test Realm" -f $HOME/PulseSecure/vpn.pulsesecure.net.der Related Links Created ByKristopher Kitajima Feedback Was this article helpful? Feedback Please tell us how we can make this article more useful. Characters Remaining: 255
Connect working on Ubuntu Linux. It's mad scientist's doc: http://mad-scientist.us/juniper.html . However, there are a few things not covered. I'll assume that you've followed mad scientist's excellent guide before going any further. openconnect juniper Issue #1: 64-bit Ubuntu By default, when you install java on your 64-bit openconnect junos pulse system, you get a 64-bit java. No surprise there, right? Well, Juniper's tools don't play nice with 64-bit java. If ncsvc you attempt to start the junipernc script you'll promptly see the "VPN has failed!" error message. VPN has failed! Also if you look closely in your Terminal you'll see the text error: https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB40158 Failed to load the ncui library. This is the clue that we are dealing with the 64-bit issue. The work around for this is to install a 32-bit java on your system. Type the following into your Terminal: sudo apt-get install ia32-sun-java6-bin After typing your password, a 32-bit copy of java will be installed at: /usr/lib/jvm/ia32-java-6-sun . Now, you need to convince Juniper Network Connect to http://holyarmy.org/2009/06/vpn-on-ubuntu-linux-with-juniper-network-connect/ use the 32-bit java. If you don't use java for much besides your new VPN, you may just want to make the 32-bit java your default. This can be done by typing the following into your Terminal: update-alternatives --set java /usr/lib/jvm/ia32-java-6-sun/jre/bin/java If you DO use java and just want to tell the VPN to use the 32-bit java, you should modify the junipernc by adding the following line right after the block of lines that start with "#": export JDK_HOME=/usr/lib/jvm/ia32-java-6-sun Now, when you run junipernc, it will use 32-bit java and you should no longer have the failure due to ncui. Issue #2: Determining Your Realm The scripting for Network Connect asks a few questions that may not make sense to a typical user. Even a networking savvy programmer may not be certain what values to use for the "Realm" or "PIN + SecureID Code". Finding your realm is fairly straight forward if you don't mind diving into some HTML. Point your web browser to your company's VPN website: https://vpn.mycompany.com or https://connect.mycompany.com . View the source of that page and look for a line like: The value of REALMNAM
a GitHub account Sign in Create a gist now Instantly share code, notes, and snippets. Star 0 Fork https://gist.github.com/6369944 0 Dieterbe/juniper_brute_force.py Created Aug 28, 2013 Embed What would you like to do? Embed Embed this gist in your website. Embed Share Copy sharable URL for this gist. Share Clone via HTTPS Clone with Git or checkout with SVN using the repository's web address. HTTPS Learn more about clone URLs Download ZIP Code failed to Revisions 1 i needed to connect to a juniper network connect vpn, but i didn't know the exact format of username, realm, hostname, and i wasn't sure exactly which password. this script uses Pexpect to try all combinations until it works. Raw juniper_brute_force.py #!/usr/bin/env python2 # must be run from your ~/.juniper_networks otherwise you authenticate with ive get: # Failed to load the ncui library.\nQuitting. # see also http://htnhan.blogspot.com/2013/07/juniper-network-connect-on-arch-linux.html import pexpect import time from itertools import product hosts = [''] users = ['youruser' , '..'] realms = ['-r foo', ..] passes = [''] error_104 = 'ncapp> Failed to connect/authenticate with IVE. Error 104' error_hostname = 'Error unable to resolve host' def test(combo): host = combo[0] user = combo[1] realm = combo[2] passw = combo[3] cmd = "/opt/bin32-jre/bin/java -jar NC.jar -h %s -u %s -f