Mitel Forums - The Unofficial Source
Mitel Forums => Mitel Software Applications => Topic started by: Saltrock23 on December 11, 2017, 11:51:39 AM
-
Having trouble setting this up keep getting Failed to Contact server
I have the right username the details i have been given are the DC primary and secondary and i can ping these using root console can it be a distgin uished name issue
my login is john.smith
OU = External Contacts
OC= Users
Dc= Fake.local
What would the distinguished name be?
currently mine is
Domain = fake.local
Distinguished name = cn=john smith,cn=external contacts,cn=users,cn=sites,dc=fake,dc=local
-
IDS Connection from Pbx or Micollab ?
-
Your Distinguished name should be like that :
CN=john.smith,OU=external contacts,OU=users,DC=fake.local
-
|From Micollab
And when i change it to your suggestion i get the same result Failed to Contact server(s)
Could this be a user account permissions issue
-
|From Micollab
And when i change it to your suggestion i get the same result Failed to Contact server(s)
Could this be a user account permissions issue
you should use OPENLDAP software to be sure that u don't have any issue with premission.
-
try :
CN=john.smith,OU=external contacts,OU=users,DC=fake,DC=local
-
Saltrock,
Are you trying to setup the IDS connection to your AD and the account you are using is not allowing it?
What I have had success with is going into the account and copying the Distinguished Name directly from the AD for that account and then pasting it in to the IDS connection page. For some reason if I tried to manually type it in then it would not work, but performing a copy/paste always seems to work.
Thanks,
TE
-
Ok so it connects via unsecure but not secure or ldaps
Could it be a domain issue as my domain for the micollab is set to fake.gg and there acutal ad domian is fake.local i am authenicating with a domian admin account on the fake.gg
-
Please share a screenshot of you conf.
-
Saltrock23,
Try using Softerra LDAP Browser and see if you can get in secure with your credentials. Most likely it is the port you are using not the domain you are set at. I had one customer using a unique port number and had a similar issue with logging in secure.
Thanks,
TE
-
Tried the software and works without SSL
Config of current IDS is attached.
We are using wildcard for all Mitel servers fake.gg and client domain for users is fake.local but it works without ssl, but need it fully working to do authenication.
-
I think the port is 636 for secure LDAP
-
if it connects without ssl then it might be that the Ad server doesnt have a certificate listing its own name
-
Saltrock23,
billbry66 is correct in that the AD has to have a valid certificate on the domain that you are looking on otherwise it will never work for the pass-through authentication.
Thanks,
TE