Hi, we have an existing ldap server in America. And here in our office in Canada, we would like to authenticate clients in our local PC's. How can I connect the ldap server here in our office? We want to authenticate clients on the server. How to configure our ubuntu OS as an ldap client? Kindly help. Thanks.

You mean HELP AGAIN???:
http://www.linuxquestions.org/questi...on-4175582740/
http://www.linuxquestions.org/questi...on-4175582412/

AGAIN, putting "how to set up ubuntu to authenticate to ldap server" pulls up:
https://help.ubuntu.com/community/LD...Authentication

Opening new threads with the same question (and under a different user ID), doesn't get you different results. AGAIN...it doesn't matter where the server is, as long as it's reachable over the network.

The LDAP Server is on another network, or subnet from my local PC. How can I make my local PC and the LDAP Server meet? Or in the same network?

looks like you don't read the answers. Can you tell us what kind of response will be accepted?
For me it works - is this a good answer?
Follow the guideline: https://help.ubuntu.com/community/LD...Authentication was posted several times. What is the problem with it?
How can we help you?

1 members found this post helpful.

AGAIN, as you've been told in your OTHER threads, and under your other user ID, IT DOES NOT MATTER WHERE THE LDAP SERVER IS. As long as you can query it over the network, then set up your LDAP client as you would for any OTHER PC. You've been handed the documentation several times now, but it appears you're just not reading/understanding the answers.

I already succeeded at authenticating my local PC with a local LDAP server. Now, i am trying to authenticate my local PC in our existing LDAP server which is not in the local/ same network. How can i do that? Our LDAP server is not accessed locally. It's in america.

I still cannot querry it, locally.

AGAIN.....IT DOES NOT MATTER WHERE IT IS LOCATED!!!!!!!

What part of that is not clear? AGAIN, as you've been asked several times now, in this and your OTHER threads for the exact same question...are you able to query the remote LDAP server from your location? If so...then set it up to use that server, the EXACT SAME WAY you set it up to use the LOCAL server, except change the name/address/port as needed. If you are NOT able to run an LDAP query against the remote server, then (as said before), talk with your network admins and GET ACCESS to it.

EDIT: Then talk to your network admins. You're asking us to provide you with details about your internal network.

you mentioned you set up a tunnel. Is that right? Does it work properly (or as expected)?

I have no idea how can I connect to an ldap server in america.... without information about how it is configured, how can I reach it ....

1 members found this post helpful.

How can i set up a tunnel correctly?? Please help.. The netadmins here said that i should use port forwarding, ldap server uses port 389.

My main problem is i cannot connect my local machine to our ldap server. I cannot authenticate it.

just googling this is the first hit:
http://inside.mines.edu/fs_home/gmur.../sshNotes.html
Read that page carefully and try to follow the process (also you can try another page). Post if you stuck somewhere, but please post what have you tried too!
and similar answers will not help YOU to go further.

So why AREN'T YOU DOING IT??? 389 is the unsecured port, and 636 is the secure port. Since you STILL (after two threads as this user, and one as your OTHER user), don't tell us version/distro of Linux you're using, or what kind of firewall/router/switch/whatever is between you and the other server, what do you think we'll be able to tell you? The VERY FIRST HIT in Google for "port forwarding iptables" is:
https://www.digitalocean.com/communi...-with-iptables

...complete with examples. If you're the administrator at your site, this should be something easy for you to do. If you're NOT, then ask your network admins to help you.
Right...which is the same thing you've posted in three threads now. Re-stating it doesn't tell us anything new.

Gentlebeings, for all we know, this exceptionally-unmotivated person could be a bot. Shouting at him won't turn his head(-lights) on.

There are basically only three possibilities to consider here:

1. The IP-address of the LDAP server might, in fact, be incorrect.
2. A firewall anywhere along the route could be blocking LDAP traffic, or refusing to accept such traffic from this "unexpected by it" IP address. (This is a wise precaution to take ...)
   • If a VPN is being used, then it, too, has traffic-filtering capability.
   • If the firewall rule is to DROP the packet rather than to REJECT it, "the packet simply disappears."
   • If the server is also programmed not to respond to "pings," its very presence on the network is difficult to detect.
3. The server is, in fact, being contacted, but it is not responding as the OP expects, and the OP either does not know how to diagnose the problem or has not yet bothered to do so.

Network services find no reason to "be helpful" to someone or something that they consider might be an intruder or an attacker. If the managers of the LDAP configuration in America have done their homework, it certainly won't be.

Of course, what the OP should do is to contact his colleagues in America for assistance, not to keep asking questions here.

According to the documentation I've been reading lately this is deprecated, kind of like implicit FTPS. So it depends on the setup. /nitpick