cancel
Showing results for 
Search instead for 
Did you mean: 

cannot connect to login TO sign in policy

Highlighted
Occasional Contributor

cannot connect to login TO sign in policy

Hello All

I just started working with the ssl vpn technology, so i'm novice in almost all the topics. We have a new ssl device and we just finished the configuration and we started the test phase. I tried to connect to one URL , but after I put my credentials in the login page and try to click in the loging page nothing happen. I tried in 3 differents explores becuse I thought it could be the issue with the explorer but I got the same results, even I do not have any issue when I tried to connect to the admin URL. So I do not know if may be something is missing in the configuration or what can be the issue. Any help on this will be really appreciated.


Best regards
9 REPLIES 9
Highlighted
Pulser

Re: cannot connect to login TO sign in policy

Hi - Its hard to guess what may be transpiring without any errors, logs, etc. It sounds strange that nothing happens when you click login.

Have you used the feature to customize sign-in pages? If yes I would check the custom sign-in pages or try with the default sign-in page.

If you have not customized the sign-in page using your own custom sign-n page package then I recommend installing some form of http sniffer (like httpwatch) to see what the browser is doing when you click sign-in. Is the request being sent to the SSL VPN server?

I'm assuming you do not see anything in the user access logs?
Highlighted
Contributor

Re: cannot connect to login TO sign in policy

Hi,

can you share the logs you see on gateway. I suspect you have not assigned any matching role for yourself.
Highlighted
Occasional Contributor

Re: cannot connect to login TO sign in policy

Hello Ruc

I downloaded the template that other ssl vpn Device that is working fine, actually I saw that the appearance of the sign in page changed even the url change, But is is like if the sign In botton is disable. How can I check the logs of user access that you mentioned?

Best Regards
Highlighted
Occasional Contributor

Re: cannot connect to login TO sign in policy

Hello Again Ruc, you are right I can not see any loging atempt in the user accees log
Highlighted
Occasional Contributor

Re: cannot connect to login TO sign in policy

Hello Kapilaks1

which logs do you want That I share, fr user access logs are empty
Contributor

Re: cannot connect to login TO sign in policy

HI Hector,

Go to User access logs and click on settings and select all the check boxes under "Select Events to Log". Let us know if you still can't see any logs for your login attempt.
Highlighted
Pulser

Re: cannot connect to login TO sign in policy

Please try with default sign-in page first, if that works you know the issue is isolated to the sign-in page your are using.
Highlighted
Occasional Contributor

Re: cannot connect to login TO sign in policy

Hello Kapilaks1

Please find below the logs for the login attempts

AUT23457 2017-06-01 19:06:11 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Login failed using auth server Symantec-VIP (Radius Server). Reason: Failed
Info AUT24327 2017-06-01 19:06:11 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Primary authentication failed for hector.grajales/Symantec-VIP from 189.211.0.33
Info AUT23457 2017-06-01 19:04:14 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Login failed using auth server Symantec-VIP (Radius Server). Reason: Failed
Info AUT24327 2017-06-01 19:04:14 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Primary authentication failed for hector.grajales/Symantec-VIP from 189.211.0.33
Info AUT23457 2017-06-01 19:02:16 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Login failed using auth server Symantec-VIP (Radius Server). Reason: Failed
Info AUT24327 2017-06-01 19:02:16 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Primary authentication failed for hector.grajales/Symantec-VIP from 189.211.0.33
Info AUT23457 2017-06-01 18:56:10 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Login failed using auth server Symantec-VIP (Radius Server). Reason: Failed
Info AUT24327 2017-06-01 18:56:10 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Primary authentication failed for hector.grajales/Symantec-VIP from 189.211.0.33
Info AUT23457 2017-06-01 18:53:48 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Login failed using auth server Symantec-VIP (Radius Server). Reason: Failed
Info AUT24327 2017-06-01 18:53:48 - ive - [189.211.0.33] hector.grajales(Remote-access)[] - Primary authentication failed for hector.grajales/Symantec-VIP from 189.211.0.


I suspect that the ssl vpn is not sending the request to the server. I monitored the traficc in my fiwall when I tried to connect and I do not see traffic from the ssl vpn to my server.
Highlighted
Contributor

Re: cannot connect to login TO sign in policy

Hi Hector,

Please note all the authentication traffic goes via internal interface therefore I assume your Symantec Auth server is on south side.

I reckon ruc that try with default sign-in page however would also suggest to check if there are any logs on your Authentication server because if server is unreachable then normally timeout errors are recorded in logs.