Network Connect (vpn client) problem on MAG6610

[joshking1_]

Hi,

Please I hope someone has seen this problem before and can help me out.

The issue I have at the moment is that when network connect is run from the web page or directly from a laptop its full connectivity is hit and miss.

Sometimes it connects with full connectivity and access to required resources, but on some other occassions the users connect with only one way transmission (no bytes received on the client). Then if they disconnect (and if lucky) reconnect maybe 2 mins later then the full connectivity is possible again.

We were using network connect version 7.0.0 and have upgraded to 7.2.0 2 months ago but the hit and missi issue is still happening.

The PCs are running windows 7 and this happens for all users connecting from different locations and internet connection.

Thanks in advance for your contributions.

Josh

[Kita_]

It will depend on where the packet is being dropped.  You'll need to run a packet capture on the client virtual and physical interface, internal port of the SA and the backend resource.  From there, you'll want to see if you see the packet is captured on both the virtual interface of the client and the internal port of the SA.  If so, then you'll need to see if the packet reaches the backend resource and if it send a response.

The only factor that doesn't make a lot of sense is they sign in and out and it works unless the NCIP is changing or another device with a conflicting ip address is coming on and offline during the issue.

[joshking1_]

Thanks Kita.

There is no issue with access to backend resources and routing to internal networks once the users connect ok.

The strange thing is that the issue has no specific pattern. There are occassions where the connections works ok straight away and some other times it just takes maybe 2 or 3 attempts to establish connections. I am still troubleshooting and also considering an upgrade to version 7.4 and also plan to test with xp machines (all users are currently on windows 7).

Thanks.

Josh