AD Connector not working anymore

[mseelig]

After the automated restart of UT services during last night, the AD Connector is not working anymore. Even test button fails. Is there any hint on the UT box where we can find out more about the error? I did not find any log file/entry on ut box showing me the underlying problem.

Any hint would be apriciated!

Thanks
Michael

[dmorris]

You can try this patch:
http://wiki.untangle.com/index.php/9...AD/RADIUS_test

It might help.

[mseelig]

Installed the patch, but no change, even rebooted the system. Want to point on that we do not only have problem with the Test Button, we really cannot log into the captive portal, because AD is not working.

Does anyone know the log file which should show the underlying AD connection error?

Michael

[mrunkel]

Please contact support so that they can help you with this issue and get you a fix as soon as one is available.

http://www.untangle.com/live-support

[mseelig]

After reinstalling, AD wasup and running, after two days it just stops to work! I would really like to see the underlying exception. Does someone knows, if it is possible to pass the exception in settings.js? I found the code, but code changes to that file are not applied, even after rebooting the server:

var message = main.getAppAddressBook().getStatusForSettings( function(result, exception) {
        if(Ung.Util.handleException(exception)) return;
    var message = result.ADWorking == true ? this.i18n._('Success!  Your settings work.') : this.i18n._('Failure!  Your settings are not correct: '+exception.message);

Anyone knows, what to do, that the changed code will be applied to be executed?

Kind Regards,
Michael

[sky-knight]

Please contact support so that they can help you with this issue and get you a fix as soon as one is available.

http://www.untangle.com/live-support

Bumping the only way you're going to fix this.

[mseelig]

Bumping the only way you're going to fix this.

What do you believe what I am doing? I have premium package and I would love to see the problem to be fixed! I reported this issues there since the beginning of this thread!! Ok, they did not find it yet, but as developer I know, that there is a hole bunch of detailed exceptions that you become if you make a mistake in LDA connection, so why should we not receive them (at least in a log file!)?

Michael

[sky-knight]

Support doesn't use these forums! At least not officially.

Also, I'm aware of two patches that DMorris created to address this issue this week alone. UT support is aware of the situation and they are the best place to put this sort of thing.

Also, all of this is being documented http://wiki.untangle.com/index.php/Patches#9.0

Which is a page everyone with 9.0 should be watching anyway.

[mseelig]

Hi sky-night

1. The information for this patch belongs to the TEST only, but for me, the login is not working as well.

2. Earlier in this thread dmorris already told me to apply this patch. Nothing changed! But then the support told me that I applied a wrong patches (however, it was the link above, I just copy&paste it...). So I was afraid to apply the patch on the new box again.

However, after your reply I applied the patch again, and now I am able to login & TEST. Hope this will be persistant...

Thanks,
Michael

[sky-knight]

I heard from support this week that the original patch had a problem. DMorris made a new patch on Wednesday I think? I just happened to ask about it while on the phone for something else. That's why I was shoving you to them, because this sort of thing changes by the hour in some cases! There is no way for the forums to keep up!

Heck, half the time the support guys are in the dark. If you have a bugzilla number for the bug in question that is really the best place to look. Because the devs stuff details into bugzilla when they "fix" it. So at least you know the patch has changed.

Which, if you're like me, bugzilla is the bane of your existence. I have no clue how the devs make heads or tails of it. The search feature has never found me the bug I'm looking for. I know it's likely me, but others have complained too.