LDAP over Putty

[s***@gmail.com]

I have setup an LDAP server. When I conntect to this server (on
192.168.1.3) from any host in the (192.168.1.*) domain, I can lookup
addresses fine. However when I forward ssh port 389 to 192.168.1.3
using putty and try to connect to LDAP server from my windows machine
things don't work.
Can anyone suggest a good way to debug this problem?
As I said, I have already forwarded port 389 and am not using secure
LDAP.

Thanks.

Sasan

[Enrique Perez-Terron]

Post by s***@gmail.com
I have setup an LDAP server. When I conntect to this server (on
192.168.1.3) from any host in the (192.168.1.*) domain, I can lookup
addresses fine. However when I forward ssh port 389 to 192.168.1.3
using putty and try to connect to LDAP server from my windows machine
things don't work.
Can anyone suggest a good way to debug this problem?
As I said, I have already forwarded port 389 and am not using secure
LDAP.

I know next to nothing about Windows and ldap, but don't you have to
configure it to use port 389 *on the local host*? I mean, "it" is Windows
or whatever applications use ldap.

Also, windows xp has a "netstat" command, so you could run netstat -a
and check that it sees something on port 386 in state "listen".

-Enrique

[s***@gmail.com]

Hi Enrique,

Thanks for your reply.

I do have port 389 forwarded to the host where the LDAP server is
running. So the configuration part is done. Also, instead of netstat, I
ran "namp" on windows to make sure LDAP is listening on port 389, which
it is!
But still no sign of the LDAP information.
I am running Thunderbird on my linux (in the LAN of the host) where I
can lookup data in LDAP , and I am running Thunderbird on Windows (with
port 389 forwarded) but I cannot get to the LDAP information. Needless
to say the LDAP configuration is the same on both platforms for
Thunderbird (except hostname which on Windows is set to localhost, and
on linux is set to the hostname in the domain that is serving the LDAP
data).

Any ideas?! Thanks.

Sasan
p.s. thanks for your articulated reply to my other post. Iwill reply
once I find a bit of extra time.

[Enrique Perez-Terron]

Post by s***@gmail.com
Hi Enrique,
Thanks for your reply.
I do have port 389 forwarded to the host where the LDAP server is
running. So the configuration part is done. Also, instead of netstat, I
ran "namp" on windows to make sure LDAP is listening on port 389, which
it is!
But still no sign of the LDAP information.
I am running Thunderbird on my linux (in the LAN of the host) where I
can lookup data in LDAP , and I am running Thunderbird on Windows (with
port 389 forwarded) but I cannot get to the LDAP information. Needless
to say the LDAP configuration is the same on both platforms for
Thunderbird (except hostname which on Windows is set to localhost, and
on linux is set to the hostname in the domain that is serving the LDAP
data).

But isn't the ssh connection going to the server that is serving the LDAP
data?

In that case, you must tell putty to forward the port to the ldap server.
Putty will tell the ssh server on the linux side to connect to the server
you say to putty.

I haven't used putty for a few years now, but the openssh client has the
option format -L [bind_address:]port:host:hostport, where host:hostport
should be the ldap server and its port. bind_address is an address on the
ssh client. A typical client can have the loopback interface, a nic for
the local network, and a ppp interface to the outside world, and most
people want the port on the client side to be available only on the
loopback interface, i.e., only to the client computer itself.

-Enrique