cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
648
Views
0
Helpful
3
Replies

WebVPN and 'Socket is closing' problem

Yossi.Mor
Level 1
Level 1

Hello Forum,

I have enabled WebVPN on the external interface of a concentrator 3005 and everything worked fine.

After few days, i was failed to access to the external interface. On the log i got the following error "Socket is closing: peer closed".

The client is W2K / XP Pro.

Any ideas why i am getting that error?

BTW when i telnet to that interface on port 443, it was ok.

Regards.

Yossi Mor

3 Replies 3

a-vazquez
Level 6
Level 6

It should work if Allow Management HTTPS sessions is check on that interface

Configuration | Interfaces |public interface

tab webvpn

check the box: Allow Management HTTPS sessions

Hi,

I am still having the same issue.

Any other ideas.

Thanks for your help.

Yossi

Hi,

I was able to resolve the issue an apparently is seems as a bug in Webvpn functionality.

In my scenario i was trying to access the external interface of the concentrator.

By default a self signed certificate is generated on the public interface and here was no problem to initiate SSL tunnel.

The problem begins when instead of the self signed certificate you generate a certificate from your enterprise CA. In this case when initiate a SSL connection to the public interface i am present with the certificate, but when i accept it i can't get the login page of Webvpn feature.

Is there a work around for that problem?

Regards.

Yossi Mor