- Pulse Secure Community
- :
- About fcbcg
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
07-24-2015
10-29-2017
fcbcg
Occasional Contributor
12
Posts
0
Kudos
0
Solutions
05-25-2017
05:29:PM
I have tested disabling the Cisco Media Services Interface Protocol Driver from the Pulse/Juniper Virtual Adapter and the windows 10 box is now shutting down correctly. Thank you for the information.
... View more
05-02-2017
05:56:PM
I am running version 5.2.7 of the Pulse client on a Windows 10 laptop. This problem did not happen on Windows 7 laptop. The client is preconfigured to do machine then user auth and to reconnect at time out or deletion. When I try to shut down the laptop with the Pulse client running, it gets to the where the screen says Shutting Down and hangs with the spinning circle and never shuts down. I saw in this topic where you asked if Jabber was running. What is the problem with Jabber? I do have Jabber running. After I saw this I tried stopping the Cisco services, which are set up as automatic, and then was able to shut down the laptop successfully. This seams to only happen when Jabber is running while the VPN client is active and I try to shut down. Is there a fix for this?
... View more
09-16-2016
03:09:PM
Users are getting the terminal session authentication problem when using the terminal session option going through browser to terminal session option on VPN page. On the appliance FIPS is not enabled and the security setting is set to Accept only TLS.
... View more
08-26-2016
05:10:PM
We are having the same issue with SSH session. Also we are having a problem with some users coming in using terminal services failing authentication with Bad Username and Password. Also on 8.1R9.
... View more
08-19-2016
06:11:PM
I would open a support ticket with Pulse. This has become a real problem for us. Small amount of users experiencing the issue with a large impact on productivity.
... View more
08-16-2016
01:39:PM
We have found looking at the debug log that the user's local computer name is being picked up by the Pulse terminal session instead of the Domain and username he is typing in at the windows prompt. Now to figure out why this is happening to this user and two other users out of hundreds of users.
... View more
08-15-2016
01:21:PM
He has the problem from any machine in his environment. If we do a webx with him and hand control over to another user's desktop out of his environment, he logs in with no issue.
... View more
08-12-2016
05:22:PM
After upgrading to version 8.1R9 we have several users (out of many) that are experiencing a problem with terminal services authentication. Once they log in and click on their terminal session link they must immediately authenticate the session. This is due to the fact this rev of code now supports NLA. Because the of this the user must now type in the Domain\UserID in the username field. This works fine with most of our users using terminal sessions. The users having the issue immediately get a failed logon box back with Username and password is incorrect, although the username and password is fine - not locked out, not expired and have permission to log into the remote computer. We have also asked the user to try different syntax in the username field - FQDN of remote computer\ID, Domain\computer name\ID, etc. The client computers are running Windows 7 and Windows 10. The destination computers are Windows 7 and server 2008. We have Pulse support engaged. So far nothing. Just wanted to know if anyone else has seen this or has some insight into why this might be happening. It seems like it must be something on the client machine that is having heartburn with the NLA. Any thoughts would be appreciated.
... View more
11-10-2015
05:07:PM
I have opened a case. It's getting to external websites that has become an issue for random users after NC is started. As you can tell we a pulling at straws trying to determine the cause. I will post if we find an answer. Thanks for your help.
... View more
11-04-2015
01:55:PM
I upgraded our QA Mag4610 to version 8.1R6 and had a user test. This user can consistently reproduce the problem of not being able to access external websites while logged in. In the past he could attempt the first time to open an external web page, fail, close IE11 and reopen the page and it worked, although some of our users could not open them at all. With version 8.1R6, he can not get the pages to open at all. I had the problem this morning after logging in and starting NC. While on the intranet site, I put the browser in Enterprise mode and then attempted an external page. It then worked fine. It appears the problem is more browser compatibility related than proxy.
... View more
11-02-2015
06:02:PM
Thank you for the quick response. It is appreciated.
... View more
10-30-2015
07:23:PM
We are running Mag4610s, code version 8.0R5. Our enterprise laptops run Windows 7 and IE 11 and Network Connect. Once NC is started laptops users are randomly having a problem getting web pages to load. There is a proxy configured in the browser - Use automatic configuration script that is in http://proxypac.aaa.com/abc.pac format. The connection profile on the appliance is set to Preserve Client Side settings. The IE settings are set via GPO. This has worked great until right after we upgraded IE from version 9 to version 11. Has anyone seen this before? Thanks.
... View more
- Tags:
- System
© 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.
