-
Getting LDAP to work over WAN was just to find out if it was working. Now that I know it works, I don't need WAN open anymore...just LAN.
-
-
The publish is set to "All" at this point and it still doesn't work. Do I need to use the LAN IP in place of the WAN IP?
-
-
What line to I edit for LAN?
-
-
Thank you for posting your file. I realized I was editing the wrong line. Now maybe I can get it to work on the LAN now that I know it actually works....I hope.
-
-
I tried adding the WAN address to ldap:/// and still nothing changes. It's like there is a hidden file somewhere that actually does something. None of the files I've seen in any posts have changed anything really.
-
-
I forgot I had started over with the stock ClearOS, so I changed the prestart.sh and it says:
-
-
I can't copy and paste the output, but it's showing this:
tcp 0 0 127.0.0.1:389 0.0.0.0:* LISTEN
7583/slapd
tcp 0 0 0.0.0.0:636 0.0.0.0:* LISTEN
7583/slapd
tcp6 0 0 :::636 :::* LISTEN
7583/slapd -
-
This LDAP Admin program is still telling me the LDAP server is down on port 389. I have ClearOS Directory set to Anonymous and All networks and I've made the changes you've suggested. I've also opened port 389 and 636 on the incoming firewall. I don't understand why it's downright denying me 389 access.
-
-
I'm on a Windows machine that is outside the LAN to set all of this up. That's why I'm accessing from the WAN. All the LAN machines need LDAP on 389.
-
-
Gateway, with WAN firewall, both 636 and 389 open on WAN. LDAP admin was working on the WAN side in my last post, but now it isn't on either 389 or 636. I may have screwed this file up.
-
Toggle Sidebar