If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
can someone send me step-by-step instructions for setting up ldap and active directory on a Kyocera machine (T/A 500 and KM 3060). i tried and its not working (maybe cuz i dont know what i'm doing...lol)
can someone send me step-by-step instructions for setting up ldap and active directory on a Kyocera machine (T/A 500 and KM 3060). i tried and its not working (maybe cuz i dont know what i'm doing...lol)
thanks!!!
Seriously, this requires an tech-analyst to setup the machine and the assistance of a systems admin on client side to complete the job
not to be surly, i am a tech (only 3 years, but a tech) i have also worked on ibm clones since 1982 (TRS-80, anyone), and mainframes. i'm not a rookie at computers.
i'm a rookie at network servers and setting something like this is a little over my head at the moment. i cant exactly "play" with the customer's network to experiment.
I'm not too familiar with the these machines, but usually setting this up is fairly straight forward. You will need a network admin to at least give you some information. You will need the ip address of the domain controller (which will also be the LDAP server) and a login with the appropriate rights. The copier should not have to be joined to the domain for this to work. Enter that info into the LDAP settings on the copier and it should work. Most machines will have a default LDAP argument that wont need to be changed (should start with dc=) However there are times when you will might need to enter the domain name into this field, or some other argument if it is a domain seperated into different Organizational Units - if this is the case, you shouldnt be setting this up (there should be an admin to do it)
Right, the System Administrator should give you the information or you show them the web page to do it themself.
You did not say, or I missed it, if you are using LDAP for email addresses or for athentication.
On all of the machines I have seen you must enter dc=domain, dc=extension in the LDAP search Base field.
i.e.
dc=copytechnet, dc=.com
if they have departments and such, then you might have modified versions of this and also more information like the department name. This example would normally allow access to the entire organization. The LDAP username and password must have access to the appropriate LDAP access levels. If you cannot get it working, have the Admin try their own user\password just to see if that is the problem.
On the same note, I only know of one organization that used LDAP internally, but none of the 5 network admins knew what to put in the copier fields - LOL
Simply put, you need the appropriate user, password, and search Base.
Ask your systems admin where in the directory the user accounts live. This should be found in an Ogranizational Unit (OU). While looking at the Active Directory (AD), take note of the Directory name at the very top of the tree as this is also important.
Also make sure that you have an account that the copier can use to access the AD unless there is anonymous access.
Once you have this information, you can then enter you search string into the copier.
I will use this picture I got from the net as an example.
In this case, if all the users are under users, then that is the OU we need to use and the domain is globomantics.com. Using this information, we can now create a search search string.
OU=Users,DC=globomantics,DC=com
So when you now do an LDAP search, the copier will look under the Users OU instead of the whole directory. This will speed up your searches.
For everyone else reading this thread, I have a quick tip that can be handy when setting up LDAP searches.
If you are unsure as to which server the domain is using for AD, use the following ping command.
ping gc._msdcs
You should get a reply from the AD server that your network is currently using. This also works on larger networks that have a DC at each site and a primary DC in a data centre or similar. You will always get a reply from your local DC.
Please don't ask me for firmware or service manuals as refusal often offends.
i didnt post an update. we had 3rd level tech support remote in. he started trying to get the AD to work with outlook express, it wouldnt cooperate. so the problem lies with the server, not the machine.
Comment