05-15-2008 09:59 PM
Hi - I'm hoping someone her can help me out before I go prematurely grey.
Over the last two days we've had about 20 users complain that they are failing to connect to the VPN. They seem to authenticate OK but Network Connect fails to launch so despite them being visible in the console they are never assigned an IP address. As a work around we can get them to log on if they start Network Connect from the start menu (usually they access via a website) but it takes somewhere between 1 and 3 minutes for the Network Connect Sign In screen to appear This is only effecting the users who cannot connect - for a majority of users this will launch in a few seconds.
We are using an SA-4000 and are still on 5.3R1 but are looking to upgrade in the near future. Does anyone have any idea why this would issue will have suddenly occured? I suspect it may have something to do with our proxy settings - we currently use an automatic configuration script pointing to a pac file but I can't work out why this is only failing for some users.
Thanks for any help!
05-16-2008 01:23 PM
Its kind of hard to say without knowing your environment. I know I always look at what changed first(perhaps you are right with the proxy). It sounds like when they use the Web to Launch network connect you have it set to autolaunch network connect? Check the user logs and perform a policy trace when one of the bad users logs in to see if you can find any additional information. Are all the users signing into the same realm and page and getting the same NC connect IP range? Try deleting cookies and cache.
Good luck and feel free to post any logs you would like me to review.
07-11-2008 08:18 AM
We are running on SA-2000, upgraded to IVE 6.1R2 for over a month now.
The Network Connect application has become extremely slow (5-6 minutes from launch to VPN tunnel establishment) when launched from the Start Menu, but very speedy (under 15 seconds) when users launch it from the "Start" button within the portal.
Until recently the NC application previously took 1-2 minutes to connect, which is understandable since it has to download and lauch Host Checker and Cache Cleaner.
The slow-down started when we changed IP addresses on the SA-2000 cluster for a network reorg; however, 5-6 minutes is not acceptable...
Anyone else experience something similar?
01-08-2009 03:10 PM
03-11-2009 07:44 AM
03-19-2009 12:23 AM
04-01-2009 09:35 AM