- Pulse Secure Community
- :
- About joels_
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
joels_
Occasional Contributor
17
Posts
0
Kudos
1
Solution
10-29-2008
08:18:AM
We have a user getting a network connect session timeout message, when the feature is disabled?? Also, the message says - 'The Network Connect session will time out due to inactivity in 71582746 minutes 35 seconds. (nc.windows.app.24052) ' Why is that happening when the feature itself is disabled?? First step is to uninstall Network Connect and let it re-install.....
... View more
10-28-2008
03:26:AM
Where are they in relation to the SSL device?
... View more
10-21-2008
08:26:AM
Your best bet would be to add the new process/service/.exe to the host check rules until the software is supported in ESAP. Unfortunately, with people adding new software to machines without letting you know, this is going to happen.
... View more
10-21-2008
08:20:AM
You have to break the cluster, change the IP addresses, then re-join the cluster.... I'd make sure I was local to do it though. just in case you can't access the devices after the initial IP change. Joel.
... View more
07-01-2008
02:52:AM
Ok, I have nailed this down to a conflict between the role session timer/timeout and the HC/NC timeouts. When the user has an ungraceful disconnect (power down/wifi out/battery out), the PC will have a session cookie valid until the idle timeout for the role (in this case 60 mins). The HC is set to check every 10 mins and idle with no activity after 20. The Network Connect then drops after around 20 mins as the HC checks fail and NC has no traffic. The session is deleted from the IVE (you can tell by watching the Active Users/Logs). At this point, if the user attempts to logon again, he gets the 'concurrent users' page and clicks 'continue' to kill the old session. Here's the problem - for some reason (something to do with the session cookie) the user is denied logon, given a message telling them that a session is already on the IVE with it's IP address. Multiple attempts to re-connect get the same message until the 60 mins idle is up. Bug or just an idle timer conflict? Ways around it? Cache Cleaner - would ensure the session is clean to start with? But is a global change and would affect the user experience. Reduce the Session Idle timout, make it closer or equal to the HC inactivity timeout? Turn off Persistent Sessions - would make sure the session is closed upon browser closure - but again, would affect the user experience....they use a custom home page so won't know that they're killing their session when closing the browser. Your thoughts?
... View more
06-17-2008
09:14:AM
There is a specific page for attachments that needs to be denied. I'll see if I can dig it up.
... View more
06-16-2008
02:18:AM
I think it's dependant on the cluster type. An Active/Passive cluster working together is recommended to be on the same subnet, although that subnet can span multiple sites if you trunk your VLANs between the sites. An active/active cluster can be on different subnets as they are effectively working seperately from each other.
... View more
05-27-2008
09:09:AM
Another option might be to have the same sign-in page for both types of user and map the role according to security posture of the machine or user at the role mapping stage. You host check the host for their cert at the sign-in level, but don't enforce. Then to map the correct user type to their relevant role, refer to the host check at the role mapping stage of the logon. If the user passed the machine cert check they get NC with full access, if they didn't, assign another role with less connectivity options. This way you can easily add-in more granular checks for extra access levels in the future.
... View more
05-27-2008
08:40:AM
Could you perhaps create your own boolean custom host check using multiple standard host checks within a Role Mapping using custom expressions? i.e. Service running AND Registry Check AND Process OR, etc, etc....?? Or is it easier to just wait for the new ESAP version? Message Edited by joels on 05-27-2008 08:42 AM Message Edited by joels on 05-27-2008 08:45 AM
... View more
05-27-2008
08:25:AM
I agree, it'll come down to your idle timeout in the Session Options for the Role in question. And maybe add a line to the Welcome page like 'to finish your session, click Sign-Out'.... Joel.
... View more
05-22-2008
03:45:AM
I have the same issue, running 5.5R1. We're looking at the idle timeouts and the possibility of turning off persistent sessions to help the issue. Cache Cleaner may also deal with it. I'd really like to find out the actual cause rather than just helping it get better....
... View more
05-12-2008
09:34:AM
It would be good to confirm this, but I'd imagine it creates a static arp entry for each user based on it's own address....like a firewall does in a static NAT scenario.
... View more
05-12-2008
09:17:AM
You can only log the session activity between the IVE and the RDP server/device. You cannot see what the user is then accessing from that device using the logging on the IVE, you'd need to log on the RDP server. Joel.
... View more
05-12-2008
09:13:AM
There's not really any need to shut them down. Just disable the cluster (otherwise known as 'breaking the cluster'), then ensure you can then connect as admin to each device. Upgrade the OS on each device in turn, ensuring they come up again ok after a reboot. Enable the cluster again. Check the cluster properties and the event log to make sure they are both ok. Done. Joel.
... View more
05-12-2008
09:06:AM
I have an SA cluster setup as active/active on 5.5R1, all connectivity for users is ok, the general useage is network connect with some access filters applied. Every now and then, users are disconnected, either for an idle time-out or host-checker timeout, when they reconnect they authenticate ok and then get the 'Existing Session Exists' page, so they click continue to kill their old session....but it fails and they have to try again. They then get stuck in this loop. When we look on the admin of the SA, a lot of the time there is no existing session. Now, I have noted that 'Persistent Sessions' are enabled, which could help this issue, as it'll kill the existing session quicker, but I don't think it's the cause.... Anyone had this or something similar? Maybe something to do with the laptop privileges? or security of the build? Thanks.
... 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.
