Great thread guy's I am just about to put in a request for enhancement with one of Junipers SE's to see if we can get this resolved. I just wanted to see if anyone had heard of any developments on the grapevin? Thanks ... View more

Are effected users experiencing any error msg's, if so please provide the message ID. Also I know it's a long shot but the only other known bug --> In a Japanese OS, sometimes MS office 2007 canÕt be launched inside SVW. (56316) ... View more

The following bug was fixed in version 5.5 R1 Build # 11711, I would recommend an upgrade Microsoft Office 2007 XML documents that include references to external files are not rewritten. (Bug 41422) ... View more

Which version of code are you runningn as the following bug was fixed in 5.3R8 release? WSAM - Fixed "IDD_TIMEOUT" error when clicked on "Sign-Out" in WSAM. ... View more

Below may shed some light the sums don't add up.... Configuring Lockout options You can configure the following Lockout options to protect the IVE and other systems from Denial of Service (DoS), Distributed Denial of Service (DDoS), and password-guessing attacks from the same IP address: Rate ‰ÛÓSpecify the number of failed sign-in attempts to allow per minute. Attempts ‰ÛÓSpecify the maximum number of failed sign-in attempts to allow before triggering the initial lockout. The IVE determines the maximum initial period of time (in minutes) to allow the failed sign-in attempts to occur by dividing the specified number of attempts by the rate. For example, 180 attempts divided by a rate of 3 results in a initial period of 60 minutes. If 180 or more failed sign-in attempts occur within 60 minutes or less, the IVE locks out the IP address being used for the failed sign-in attempt. Lockout period ‰ÛÓSpecify the number of minutes you want the IVE to lock out the IP address. NOTE: Lockout options are not available to IVS systems. All other security options are available to IVS systems. The IVE reacts quickly to an attack that persists, and then gradually becomes less restrictive when the attack subsides. After a lockout occurs, the IVE gradually recovers by maintaining the Rate . If the current failure rate since the last lockout exceeds the specified Rate , the IVE locks out the IP address again. If the failure rate is less than the specified Rate for the period of Attempts/Rate , the IVE returns to the initial monitoring state. For example, if you use the following settings for the Lockout options , the IVE locks out the IP address for the time periods in the following scenario. Rate =3 failed sign-in attempts/minute Attempts =180 maximum allowed in initial period of 60 minutes (180/3) Lockout period =2 minutes During a period of three minutes, 180 failed sign-in attempts occur from the same IP address. Because the specified value for Attempts occurs in less than the allowed initial period of 60 minutes (180/3), the IVE locks out the IP address for 2 minutes (4th and 5th minutes). In the 6th minute, the IVE removes the lock on the IP address and begins maintaining the rate of 3 failed sign-in attempts/minute. In the 6th and 7th minutes, the number of failed sign-in attempts is 2 per minute, so the IVE does not lock the IP address. However, when the number of failed sign-in attempts increases to 5 in the 8th minute, which is a total of 9 failed sign-in attempts within 3 minutes, the IVE locks out the IP address for 2 minutes again (9th and 10th minutes). In the 11th minute, the IVE removes the lock on the IP address and begins maintaining the rate of 3 failed sign-in attempts/minute again. When the rate remains below an average of 3/minute for 60 minutes, the IVE returns to its initial monitoring state. ... View more

I have found IVE Platform version 6.4 R1 Build # 14063 to be stable and it has various bug fixes for Vista and Firefox users. - The following issue is fixed - Log Upload for Host Checker and Cache Cleaner applications donÕt work through Firefox with proxy. This includes all versions of Firefox. - On Vista platform with Java delivery when both HC and CC is enabled for a realm, HC is not installed - On Vista with Protected mode off, java delivery and HC in post-auth, if all HC policy pass, the user sees a sign-in page with authentication failure message. - This issue is fixed in this release: When Outlook plug-in is installed through Firefox, the User IDÓ and RealmÓ fields are empty in the Provide server detailsÓ page. These fields should be auto populated. etc .... ... View more

Are you able to show me the rest of the Firefox Java Console screen shot, the error seems to be incomplete just needs scrolling to the right slightly to piece it together? ... View more

Here are a few reasons why you may have high Memory Utilisation - Currently the SA has a limitation of not able to support heavy usage of PDF rewriting due to high memory usage. Enabling the IF‐MAP client feature on an IC or SA Device, may cause memory and device resources to be consumed if there are issues establishing a connection to the IF‐MAP Server. Be sure to disable the IF‐MAP functionality when not in use and ensure connectivity problems are resolved when IF‐MAP is enabled. Hardware Failure... Thanks Matt JNCIA-FWV JNCIS-FWV ... View more

Juniper have no existing issues with any Novell products over their NC solutions. I would recommend this as a viable solution. ... View more

Is the issue isolated to this specific client? If so please obtain a HijackThis log for my viewing. http://download.cnet.com/3001-8022_4-10227353.html ?spi=508cd2e98a589de5a4f2f5d388f3fca5 Also is the SA throwing up any errors for this client? Thanks Matt  JNCIA-FWV JNCIS-FWV Thanks Matt JNCIA-FWV JNCIS-FWV ... View more

If Cisco VPN Client 4.8 is installed on the same client machine, accessing shared folder when Network Connect is running, you may see a blue screen. Thanks Matt JNCIA-FWV JNCIS-FWV Thanks Matt JNCIA-FWV JNCIS-FWV ... View more