Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 26 subscribers
  • Views 1611 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Local User: login in userportal on in LAN

Ganimede Dignan

Hi,

 

we have created some local users, instead AD users that we use normaly. It's strange but, this local user, can login in userportal only from LAN. AD user can login also on WAN.

It is used for VPN client downlaod. Have you got any idea?

 

Thank you.



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi  

    Thank you for reaching out to the Community! 

    What is the firmware version on the firewall? I was able to access the user portal on the WAN interface with local and AD users in my LAB. 

    Is there any error message when local users try to access the user portal? 

    Thanks,

Reply
  • FormerMember
    0 FormerMember

    Hi  

    Thank you for reaching out to the Community! 

    What is the firmware version on the firewall? I was able to access the user portal on the WAN interface with local and AD users in my LAB. 

    Is there any error message when local users try to access the user portal? 

    Thanks,

Children
  • 0 in reply to FormerMember

    Hi,

     

    I'm sure that in the past it works fine. I've used SFOS 17.5.12 MR-12 and SFOS 18.0.1 MR-1-Build396

    Same user/password can login in LAN but not from WAN.

    The error messa was: Login failed

     

  • FormerMember
    0 FormerMember in reply to Ganimede Dignan

    Hi  

    I would advise you to put the access_server process in debug, replicate the issue and provide logs in debug. 

    Follow this KB Article to SSH into the XG firewall: Sophos XG Firewall: How to SSH to the firewall using PuTTY utility

    Select Option 5 (Device Management) > Option 3 (Advance Shell)

    Run this command to put the access_server service in debug:

    • service access_server:debug -d -s nosync

    Once you capture the access_server logs in debug, run the same command to put access_server service in normal running mode. 

    Run this command to check service status :

    •  service -S | grep access_server

    SFVUNL_VM01_SFOS 17.5.11 MR-11# service -S | grep access_server
    access_server RUNNING,DEBUG

    Please PM me the logs and user name. 

    Thanks,