Help - Search - Members
Full Version: DNS Resolution Fails
Kaspersky Lab Forum > English User Forum > Protection for Small and Medium Businesses
kwabbernoot
Hi,

There seems to be an incompatibility issue between Kaspersky Anti Virus 6.0 and Juniper SSL VPN using the Windows Secure Application Manager (WSAM)

Problem: DNS resolution fails completely whenever both of them are installed on the system.

I already tried several resolution:
- Completely disabeling the Kaspersky options has no effect
- Stopping the Kaspersky Service has no effect
- Adding the Juniper/Neoteris directory (incl Subfolders) into the trusted zones (any task) does not resolv the issue.

The service "DNS Client" is started but a manual restart results in "ERROR 1714: No protocol sequences have been registered"

At this time the only solution is to remove one of the products, after removal DNS resolution is restored.

Because our clients really need the VPN connectivity their only option is currently to downgrade Kaspersky Antivirus 6.0 to version 5.0 or to replace it by another Anti Virus software.

Reproducing the problem is fairly easy, it always occurs whenever both softwares are installed. On rare occations the PC did not even want to boot and one of the softwares had to be removed in "Safe Mode" to be able to normally boot the machine.

I also tested the latest beta 6.0.1.401 but also this release has the issue.

Does anyone have a clue why this strange behaviour could occur and is there a workaround/solution available ?

Regards,
Kwabbernoot
sranderle
I am running into the same issue at home.

Our VPN solution installs:
Citrix ITA Web Client
Juniper Networks Host Checker
Juniper Networks Secure Applications Manager


Is there any fix/workaround other than uninstalling software?





QUOTE(kwabbernoot @ 18.10.2006 04:04)
Hi,

There seems to be an incompatibility issue between Kaspersky Anti Virus 6.0 and Juniper SSL VPN using the Windows Secure Application Manager (WSAM)

Problem: DNS resolution fails completely whenever both of them are installed on the system.

I already tried several resolution:
- Completely disabeling the Kaspersky options has no effect
- Stopping the Kaspersky Service has no effect
- Adding the Juniper/Neoteris directory (incl Subfolders) into the trusted zones (any task) does not resolv the issue.

The service "DNS Client" is started but a manual restart results in "ERROR 1714: No protocol sequences have been registered"

At this time the only solution is to remove one of the products, after removal DNS resolution is restored.

Because our clients really need the VPN connectivity their only option is currently to downgrade Kaspersky Antivirus 6.0 to version 5.0 or to replace it by another Anti Virus software.

Reproducing the problem is fairly easy, it always occurs whenever both softwares are installed. On rare occations the PC did not even want to boot and one of the softwares had to be removed in "Safe Mode" to be able to normally boot the machine.

I also tested the latest beta 6.0.1.401 but also this release has the issue.

Does anyone have a clue why this strange behaviour could occur and is there a workaround/solution available ?

Regards,
Kwabbernoot
*
kwabbernoot
QUOTE(sranderle @ 8.01.2007 15:23)
I am running into the same issue at home. 

Our VPN solution installs:
Citrix ITA Web Client
Juniper Networks Host Checker
Juniper Networks Secure Applications Manager
Is there any fix/workaround other than uninstalling software?
*


Yes the problem is solved,

But you need to upgrade your Juniper SSL VPN application with IVE 5.3R9 Build 11419.

The release notes of this version of IVE include this line:
QUOTE
4. CS WSAM - Fixed DNS lookup issue when WSAM is installed on PC with Kaspersky AV 6.0 44250

This is a maintenance release and is not available for the general public at the Juniper Site. You need to contact Juniper support to be able to download this version of IVE.

I tested it on our test environment and with this release of WSAM DNS resolution is functional with the Kaspersky AV 6.
The kaspersky version used during the test was 6.0 build 411.

One other thing: You need to install Microsoft Patch 884020 for WSAM to work on XP SP2.

With kind regards,
Kwabbernoot
sranderle
I'll have to check my patches when I get home. I rebuilt my PC last weekend, and applied all critical patches. So KB884020 may already be applied.

As far as the Juniper MR, is this something that is applied at a remote PC or at the Juniper appliance? Is the patch for their Secure Applications Manager?



Thanks for your help



QUOTE(kwabbernoot @ 9.01.2007 04:13)
Yes the problem is solved,

But you need to upgrade your Juniper SSL VPN application with IVE 5.3R9 Build 11419.

The release notes of this version of IVE include this line:

This is a maintenance release and is not available for the general public at the Juniper Site. You need to contact Juniper support to be able to download this version of IVE.

I tested it on our test environment and with this release of WSAM DNS resolution is functional with the Kaspersky AV 6.
The kaspersky version used during the test was 6.0 build 411.

One other thing: You need to install Microsoft Patch 884020 for WSAM to work on XP SP2.

With kind regards,
Kwabbernoot
*
sranderle
Would it be possible for you to send me the patch?
kwabbernoot
QUOTE(sranderle @ 9.01.2007 18:20)
Would it be possible for you to send me the patch?
*


The patch is for the Juniper Applians that provides the VPN service not for the client that makes usage of the VPN.

In fact it is a new version of the IVE OS that runs on the Juniper appliance that you use (the service hat provides the VPN access).
If this access is provided by your company then the administrators of the Juniper SSL appliance need to upgrade their IVE OS Version.

After the upgrade of the appliance it will upgrade your WSAM whenever you logon to the VPN service.

If the admins will not upgrade then you need to downgrade your Kaspersky Virusscan to version 5.x or another virusscan software.

Regards,
kwabbernoot
21Rouge
QUOTE(kwabbernoot @ 9.01.2007 05:13) *
Yes the problem is solved,

But you need to upgrade your Juniper SSL VPN application with IVE 5.3R9 Build 11419.

The release notes of this version of IVE include this line:

I tested it on our test environment and with this release of WSAM DNS resolution is functional with the Kaspersky AV 6.
The kaspersky version used during the test was 6.0 build 411.


So crazy that I almost have the exact same problem! Please refer to post 88 and beyond in this thread:

http://forum.kaspersky.com/index.php?showt...48619&st=80

However what is interesting is this conflict seems to be still existing with version 7 of Kaspersky huh.gif

And you originally posted in late 2006. Isnt it likely that my wifes company is using the latest build of the Juniper SSL VPN application by now ie September 2007?

If not I can imagine it will be impossible to have them upgrade at the request of one affected employee mad.gif .

(I am right in saying that the upgrade happens at the company's side not on our lowly home computer...right?)

Any advice?
Whizard
I will pass this case along to TestLab.
21Rouge
QUOTE(Whizard @ 29.09.2007 10:20) *
I will pass this case along to TestLab.


That would be great.

I would have thought any problems with KAV and Juniper would have been resolved in release 7.

I am not hopeful that I will be able to get my wife's company to update "Juniper". But also it maybe the case that they are using the latest build since according to kwabbernoot there was an update to Juniper in late 2006 that resolved the problem with KAV *6*...so why the problem with KAV 7 in late 2007? huh.gif
Whizard
Because Network Layer driver was re-written from sratch. And it seems like this problem slipped by. I suggest you open a support ticket and point them to this thread http://kaspersky.com/helpdesk.
21Rouge
I have submitted the case as of 1:15 pm EST.
Whizard
Hello,

I just heard from testlab and they require more information. Please private message Kulich and ask him which details they require.
21Rouge
QUOTE(Whizard @ 2.10.2007 10:40) *
Hello,

I just heard from testlab and they require more information. Please private message Kulich and ask him which details they require.


I just saw your latest post today sad.gif. I have PM Kulich as we speak.
Whizard
Cool, lets get this case moving smile.gif
MCNB
QUOTE(Whizard @ 11.10.2007 13:43) *
Cool, lets get this case moving smile.gif


I'm having this issue too (KAV 7 vs Juniper). Have followed this and the other thread, am contacting my employer to find out their version of Juniper. Hope you all are able to make some headway from the KAV side!
21Rouge
QUOTE(MCNB @ 13.10.2007 21:36) *
I'm having this issue too (KAV 7 vs Juniper). Have followed this and the other thread, am contacting my employer to find out their version of Juniper. Hope you all are able to make some headway from the KAV side!


My wife's employer will not upgrade their version of Juniper. I believe the the problem first surfaced with v6 so I would have hoped that Kaspersky would have made changes in version 7 so that one wouldnt need to depend on Juniper to resolve the difficulty.
21Rouge
Just wondering if 2 years later KIS/KAV and Juniper can now coexist?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.