Cisco VPN client dropout problems when using Novell Client

I have some remote VPN workers who are experiencing a weird dropout problem with their Cisco VPN Client. At completely random times they suddenly lose connection to corporate email and intranet but not to their Novell mapped drives. The VPN padlock is still locked and they can still transfer files back and forth from their Novell mapped drives but cannot ping anything or connect to tcp applications like Groupwise or our Intranet. If I send a ping I see the packet being encrypted down the tunnel but nothing coming back. Users without the Novell Client installed never experience this problem and can stay connected to the VPN indefinitely. I have tried switching users from our ASA5540 to a PIX515E but the problem remains. There is nothing in the VPN log to indicate the problem and I have also sniffed the VPN adapter and again seen nothing causing this. I can find nothing on Novell or Cisco forums,  has anyone experienced this and found a solution??
EdSchwarzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lrmooreCommented:
Have you tried an update to the client? 5.0.04.0300 is the latest
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
acerimmer10Commented:
Hi,
I have users on VPN with Novell Client and have never seen this problem, but I have had something similar happen internally and found that it was issues with power management then disconnecting the PC from the network.
Is this happening when they leave their machine for a while or while they are working?
Have you looked at the VPN log?
Have you made sure that both clients (VPN + Novell) are up to date?
0
EdSchwarzAuthor Commented:
Hi there, thanks for the responses

I thought it may have been power management but i'm sure it's related to the Novell client  -  my laptop never experienced the problem (and I used the VPN client every day) but when this problem became apparent I installed the Novell client (same version used by majority of affected users) and the problem occured within an hour!  Plus the VPN is actually staying up ( I can still transfer files to and from shared drives) but I lose the ability to ping anything or http to our intranet or connect to our tcp email client etc

They are saying it is happening whilst they are actively working away (they usually get a Groupwise tcp error message indicating that the problem has occured)

The VPN log indicates no problems and I can continue to see ISAKMP & IPSec keepalives etc being sent up and down the tunnel.

We are trialling the latest Novell client today so this may well solve it but I know that there are various images out there and multiple versions of the Novell client being affected by this

I'll update once we have tested the latest Novell client
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

lrmooreCommented:
There is also an update to the Cisco VPn client. 5.0.04.0300
0
EdSchwarzAuthor Commented:
Well, we've now discovered that people without the Novell Client installed are getting this dropout as well so that was a red herring  -  also the PIX515 problem is not the same so it's just  the ASA5540 we're experiencing this on

I have tried the latest version of the VPN Client but no difference, in fact no version of the client seems to be immune fom this

Reloading the ASA hasn't worked so I've faulted it out to our Cisco Support

I have shared the points between the two contributors  -  thanks for trying
0
lrmooreCommented:
Let us know what you come up with from Cisco.
Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.