Failed To Authenticate With Ive. Error 10
Contents |
via machine credentials failure on Windows 8 and 10, but works with Windows 7 KB22739 - [SBR] Unable to juniper pulse linux assign the profile to a LDAP user KB40155 - Role-mapping and juniper network connect linux resource policy rules are missing after upgrade to 8.2R1 KB23640 - Unable to connect to a Windows juniper vpn ubuntu 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 openconnect juniper 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
Openconnect Junos Pulse
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
JuniperForum.com » Security » Remote Access SSL VPN/UAC/MAG, Pulse, and
Ncsvc
SBR (Moderators: muppet, screenie.) » Topic: Network Connect - Linux msjnc - Failed to authenticate with IVE. Error 5 « previous next » Print Pages: [1] execution of nc jar ncsvc failed Author Topic: Network Connect - Linux - Failed to authenticate with IVE. Error 5 (Read 8280 times) bytesize Newbie Posts: 2 Karma: +0/-0 Network https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB40158 Connect - Linux - Failed to authenticate with IVE. Error 5 « on: September 19, 2009, 01:26:33 pm » Hello all,I am using a Juniper SSL VPN with Ubuntu Linux. The SSL VPN requires a client certificate in order to connect. I have imported my client certificate into FireFox, http://www.juniperforum.com/index.php?topic=9311.0 and when I login using FireFox and launch the Network Connect utility I am able to access and browse the LAN.The problem is that I want to run Network Connector without having to login using FireFox first.My login is being refused with the error message: "ncapp.error Failed to authenticate with IVE. Error 5" and I can see a redirection to "welcome.cgi?p=no-cert"I think the problem is that when run in standalone mode, Network Connect is not sending my client certificate.How can I add a client certificate when running from the command line?Command:Code: [Select]./ncsvc -h vpn.mycompany.com -u bytesize -p password -f junipercertificate.crt -L 5Logfile:Code: [Select]20090919195602.146903 ncsvc[4292] dsclient.info <-- 200 (authenticate.cpp:168)
20090919195602.147224 ncsvc[4292] dsclient.info state: kStateLogin (dsclient.cpp:278)
20090919195602.147762 ncsvc[4292] dsclient.info --> POST /dana-na/auth/url_default/login.cgi (authenticate.cpp:136)
20090919195602.148441 ncsvc[4292] http_connection.para Entering state_start_connection (http_connection.cpp:277)
20090919195602.157531 ncsvc[4292] http_connection.para Entering state_continue_connection (http_connection.cpp:294)
20090919195602.158001 ncsvc[4292] http_connection.para Entering state_ssl_connect (http_connection.cpp:463)
20090919195602.274653 ncsvc[4292] dsssl.para SSL connect ssl=0x947cc18/sd=4 co
Start here for a quick overview of the site Help Center Detailed answers to http://serverfault.com/questions/243707/juniper-s-network-connect-ncsvc-on-linux-host-checker-failed-error-10 any questions you might have Meta Discuss the workings and http://holyarmy.org/2009/06/vpn-on-ubuntu-linux-with-juniper-network-connect/ policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site failed to for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Juniper’s Network Connect ncsvc on Linux: “host checker failed, error 10” up vote 2 down failed to authenticate vote favorite I’m trying to log in to a Juniper VPN with Network Connect from a headless Linux client. I followed the instructions and used the script from http://mad-scientist.us/juniper.html. When running the script with --nogui switch the command that gets finally executed is $HOME/.juniper_networks/network_connect/ncsvc -h HOST -u USER -r REALM -f $HOME/.vpn.default.crt. I get asked for the password, a line “Connecting to…” is printed but then the programm silently stops. When adding -L 5 (most verbose logging) to the command line, these are the last messages printed to the log: dsclient.info state: kStateCacheCleaner (dsclient.cpp:280) dsclient.info --> POST /dana-na/cc/ccupdate.cgi (authenticate.cpp:162) http_connection.para Entering state_start_connection (http_connection.cpp:282) http_connection.para Entering state_continue_connection (http_connection.cpp:299) http_connection.para Entering state_ssl_connect (http_connection.cpp:468) dsssl.para SSL connect ssl=0x833e568/sd=4 connection using cipher RC4-MD5 (DSSSLSock.cpp:656) http_connection.para Returning DSHTTP_COMPLETE from state_ssl_connect (http_connection.cpp:476) DSHttp.debug state_reading_response_body - copying 0 buffered bytes (http_requester.cpp:800) DSHttp.debug state_reading_response_body - recv'd 0 bytes data (http_requester.cpp:833) dsclient.info <-- 200 (authenticate.cpp:194) dsclient.error state host checker failed, error 10 (dsclient.cpp:282
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. Issue #1: 64-bit Ubuntu By default, when you install java on your 64-bit system, you get a 64-bit java. No surprise there, right? Well, Juniper's tools don't play nice with 64-bit java. If 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: 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 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 REALMNAME is what you'll need to enter when prompted. Your IT department may or may not know what this is if you as