cancel
Showing results for 
Search instead for 
Did you mean: 

Error 23791while connecting to SSL VPN

Gauravdhingra_
Occasional Contributor

Error 23791while connecting to SSL VPN

Hello,Can anyone Please suggest why sometimes i am getting this error ? and how can i resolve with this issue.

Pls give me proper solution, I tried in disabling firewall, disabling antivirus from my laptop but didnt work though.

Details of my Device- 5.5R6 (build 12857)

5 REPLIES 5
ChristopherHowar
Contributor

Re: Error 23791while connecting to SSL VPN

Hi there,

The Network Connect error message: 23791 specifically means that the secure gateway denied the connection request from this client. As it appears that the secure gateway is denying your connection, please contact your system administrator (assuming that is not you) and he/she will trace your connection attempt in the logs which may shed more light on the reason for your rejection.

Gauravdhingra_
Occasional Contributor

Re: Error 23791while connecting to SSL VPN

Are you intrested to see logs (Net connect) Please advise so that i will provide you required info, I need resolution for this issue as its been thre for long time .

thnaks

Gaurav

ChristopherHowar
Contributor

Re: Error 23791while connecting to SSL VPN

Gaurav,

I am sorry not to reply sooner to your email. If this issue is still ongoing, please raise a case with JTAC and supply the logs mentioned.

SonicBoom_
Regular Contributor

Re: Error 23791while connecting to SSL VPN

i have found that if a user is not mapped to a role that you will get the denied connection error.
kenlars_
Super Contributor

Re: Error 23791while connecting to SSL VPN

If a user is not mapped to a role, he/she is kicked back to the login page with a message like "You are not allowed to log in".

There seem to be hundreds of reasons for this message. In fact, it might be interesting to start a thread to allow people to document what they found when diagnosing it.

In our case, the most likely culprit has been the inability of the IVE to assign an address to the NC session. We've seen the following reasons -

(1) Exhaustion of an address pool

(2) Use of a static address already in use

(3) Unmatching configuration between the network NC settings and the NC connection resource policies

In this case, there is a message in the user log which confirms this.

Hope this is helpful.

Ken