Network Connect vs. Pulse?

[df_]

We have been using Network Connect for quite a few years and it works well for our users who travel all over, and the ESP to SSL fallback works great for sites that may only allow HTTPS and HTTP traffic out of their network.

What are the reasons that we would want to switch from Network Connect to Pulse? We are planning on upgrading to 7.2R1.1 and not sure if we should stick with Network Connect, or move to Pulse 3.\

Thank you.

[AJA_]

You have all the information that you require in this link:

http://www.juniper.net/us/en/products-services/software/junos-platform/junos-pulse/

Hope that helps.

Please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks

[zanyterp_]

It is really your call based on your user need; are there specific items you like about one or the other?

[AJA_]

Was the link helpful?

Do you have any more questions?

If the link I gave helped you decide, may I ask you to please mark this post as 'accepted solution' if this answers your question that way it might help others as well, a kudo would be a bonus thanks

[zanyterp_]

Pulse 3.0 has additional flexibility when it comes to upgrades. Unless there are user-training concerns, Pulse 3.0 is a great move.

[SonicBoom_]

Pulse will also be replacing NC in the future, here is a older link for the same question

https://forums.pulsesecure.net/topic/pulse-connect-secure/63341-choosing-between-the-network-connect...

[df_]

---

@zanyterp wrote:

It is really your call based on your user need; are there specific items you like about one or the other?

---

Pulse looks interesting for the ability to automatically detect if on the company network or external and automatically login if you save your password. We have been using Network Connect with Host Checker for years without any problems and it has been really stable. I am not sure if we will run into application compatibility issues or stability issues with Pulse 3.0.1 on 7.2R1.1.

It would require less testing to stick with Network Connect, but Pulse does appear to have some nice features. Staying with network connect would also make it easier for our end users since it wouldn't require additional training or documentation to use.

Has anyone run into problems with certain applications or network traffic not working properly with pulse, or any stability issues? We are running Windows 7 x64.

Thank you.

[PReinie]

If you ever have to use Switch User, Pulse Secure drops the VPN connection, but Network Connect does not, so you can switch to a different user.

Perhaps someone can let me know of a setting where Pulse Secure will not drop the VPN connection.

We've also found that Network Connect more reliably and clearly lets you know if your RSA token needs syncronization. Pulse Secure may not try to synchronize, or if it does, any message you get may be unclear, just asking for the password (RSA passcode) again.

[zanyterp]

yes, Pulse is designed to not allow switching users (and was not something that should have been working with Network Connect).
can you open a case on the RSA synchronization issue, please? both softwares use the same technology to connect to the backend and if the RSA server is saying a synchronization is needed, Pulse should pass that on to the user just as network connect did