Windows RT Client, for Juniper's Network Connect?

[mike1294_]

How were you able to choose your "Type of sign-in info"? The Type, User name, and Password are greyed out for me.

This screenshot is from an Surface RT. Its the same thing on a Surface Pro.

[nbe_]

Once you save the settings and connect to the VPN, it will prompt you for a realm then ask for your credentials.  It worked for me on RT 8.1 once I set up a test realm that wasn't using host checker.

[untruenorth_]

That's *really* interesting - and gives me hope.  Although it doesn't behave that way for me...

When you say you set up a realm with no host checker, and it prompts you for the realm, did you actually mean that it propted you for the role?

What version are you running on the appliance?

--Chris

[ruc_]

This might help:

http://www.juniper.net/techpubs/software/pulse/guides/j-pulse-windows-inbox-client-qsg.pdf

[mike1294_]

Thanks Ruc for the link to the Quick Start Guide.

We are on 7.3R7 and the guide says its supported on 7.4 so that might be why its not working. Error we are getting is "Invalid parameter."

What I'm not clear on is if the Windows in-box Pulse client allows certificate authentication.

[nbe_]

It looks like the version included with full Windows 8.1 Pro still has Windows RT in the user agent.  I was looking into restrcting only RT to a role without hostchecker.  I'll be interested to see the SoH/NAP integration if that becomes available.

User Agent on 8.1 Pro:

Junos-Pulse/7.4.0.0 (Windows RT) JunosPulseVpn/1.0.0.206

[gabadoo_]

So for some reason I cannot connect to a url that has a slash.  for vpn.whatever.com it prompts me for a password.  But the URL I'm supposed to connect to is something ling vpn.whatever.com/slash123.  It tells me that it's an invalid paramter.

[zanyterp_]

I'm not sure if the "/" URL is supported at this time.
I believe certificate authentication is supported

[ruc_]

1. Yes Client Certificate based auth is supported.

2. Unfortunately at this time the user-agent string is the same on Windows RT and Windows Pro platforms.
3. And using slash (i.e) URL rather than hostname/ip  is not supported through the UI. However you could use the PowerShell script option described in the doc and use the URI parameter as a workaround. 

[mike1294_]

Thanks Ruc for clarifying. I was trying a URL https://vpn.example.com/mobile and it wasnt working for me. Getting error  "Invalid parameter.". I'll try the Powershell way.