Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 3 subscribers
  • Views 5108 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

Proxy Authentication Pop up

drahthaar
Why would I be getting the proxy authentication popup at the same time everyday at 8:30 am EST.  If the user waits 5 min then everything will be working fine.

It is an ASG220 firmware version 7.510.

Any help would be appreciated.


This thread was automatically locked due to age.
  • 0
    Can anyone tell me where to look in the logs to see what would be causing this.  I have been trying to track this down for the past week and can't see anything that would be causing it.
  • 0 in reply to drahthaar
    Also,  when this happens, it won't let me login to the machine.  It tells me invalid username and password
  • 0
    Are you using the Astaro Authentication Agent?  If not, what form of authentication is the Web Proxy set to use?
  • 0
    Try checking the User authentication daemon log.
  • 0 in reply to Scott_Klassen
    2011:10:20-08:26:10 vpn2 aua[26301]: id="3006" severity="info" sys="System" sub="auth" name="Trying xx.xx.xx.xx (adirectory)"
    2011:10:20-08:26:10 vpn2 aua[26301]: id="3006" severity="info" sys="System" sub="auth" name="Trying xx.xx.xx.xx (radius)"
    2011:10:20-08:26:15 vpn2 aua[26301]: id="3006" severity="info" sys="System" sub="auth" name="failed to recv packet from radius server: timed out waiting for packet (ETIMEOUT)"

    2011:10:20-08:26:15 vpn2 aua[26301]: id="3005" severity="warn" sys="System" sub="auth" name="Authentication failed" srcip="xx.xx.xx.xx" user="***x" caller="webadmin" reason="DENIED"
    2011:10:20-08:32:53 vpn2 aua[27181]: id="3006" severity="info" sys="System" sub="auth" name="Trying xx.xx.xx.xx (adirectory)"
    2011:10:20-08:32:54 vpn2 aua[27181]: id="3006" severity="info" sys="System" sub="auth" name="Trying xx.xx.xx.xx (radius)"


    It looks like it failed to recv a packet from AD,  and then tried again 5 minutes later and it worked then.
  • 0
    You may want to check what's being logged on the DC side for these events.  Due to the third line posted, you'll also want to check for network issues between the Astaro and your DC, such as auto-negotiation mismatches or a port going bad and dropping packets.
  • 0 in reply to Scott_Klassen
    Do you know what it gets in the "packet"?  authenticated users?

    I was on the same page as you,  possible network interruption based on the third line.
  • 0
    Do you know what it gets in the "packet"?
    Which "it"?  The initial authentication request from the Astaro to the DC will have username and password.  The reply will be either authentication succeeded or failed.